chore(release): 0.20.14 coordinated (npm/PyPI/NuGet 0.20.14 · Maven 7.20.14)

Coordinated at the shared patch number per the single-shared-patch policy set at
0.20.13. Every changed product file is npm-only: the migrate snapshot fix lives
in @metaobjectsdev/cli, and the corrected agent-context ships via
@metaobjectsdev/sdk — the only package on any registry that bundles the
repo-root agent-context/ tree. The Python wheel vendors none (its build hook is
an explicit no-op), and both `dotnet meta agent-docs` and the Maven AgentDocsMojo
are redirect stubs to the Node CLI. PyPI, NuGet and Maven Central are therefore
version-parity bumps with no changed product file.

PATCH, not MINOR. Every behavior change converts a previously BROKEN flow into
the documented one — day-1 `--from-db … --apply` followed by the documented day-2
offline incremental used to die with `no schema snapshot`, and the `--apply`
variant left the next offline diff re-emitting applied DDL as an un-appliable
duplicate. No invocation that previously succeeded now fails or degrades, the
snapshot write is guarded (dry-run, blocked, refused and apply-failed runs leave
it untouched), and `meta gen` output is byte-identical. That is the table's
"wire behavior fixed to match the documented contract" row, reinforced by
"output change = pure bugfix". The "changed CLI semantics" clause sits in the
public-API-BREAKING row, whose company is removed exports and newly-required
params; precedent agrees — 0.20.7 shipped a whole new subcommand as PATCH.

Also amends docs/RELEASING.md, which still documented the superseded
per-registry-scoping rule ("no release for that registry") and twice asserted
versions are not unified. Those predate the 0.20.13 policy and contradicted it,
which would have recurred every release. The header, the change-class table row
and the tail note now state the standing rule: all four registries cut at the
same minor.patch, with a version-parity bump where a port has no changed file.
Stale "currently 0.19.7 / 0.19.9 / 7.11.7" references refreshed to 0.20.13.

Verified before promoting: CI green on 91de3a8; all 14 packages published to
`next` as 0.20.14-rc.1; packed sibling deps pinned to the release version with no
workspace:* leakage; and an external install of the RC in a fresh directory under
BOTH npm and pnpm-strict, exercising the actual fix — day-1 --from-db --apply
writes the snapshot, day-2 offline incremental emits a real migration.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S3msoGxjRMwx94PhKSLDuE

Author: dmealing

CHANGELOG.md

@@ -7,11 +7,16 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
-**Scope: npm · PyPI · NuGet** — Maven Central has no changed product file (its
-`AgentDocsMojo` no longer scaffolds agent context; it redirects to the Node CLI).
-The migrate fix is npm-only (`@metaobjectsdev/cli`); the agent-context correction
-ships wherever the scaffolded skills ship — `@metaobjectsdev/sdk` on npm, the
-bundled content tree in the PyPI package, and the C# CLI on NuGet.
+## [0.20.14] — npm `0.20.14` · PyPI `0.20.14` · NuGet `0.20.14` · Maven `7.20.14`
+
+**Scope: npm `0.20.14` · PyPI `0.20.14` · NuGet `0.20.14` · Maven Central `7.20.14`** —
+coordinated at the shared patch number per the single-shared-patch policy ([0.20.13]).
+Every changed product file is npm-only: the migrate fix lives in `@metaobjectsdev/cli`,
+and the corrected agent-context ships via `@metaobjectsdev/sdk` — the only package on
+any registry that bundles the repo-root `agent-context/` tree (the Python wheel vendors
+none, its build hook is a no-op; the C# `dotnet meta agent-docs` and the Maven
+`AgentDocsMojo` are redirect stubs to the Node CLI). PyPI, NuGet and Maven Central are
+version-parity bumps with no changed product file.
 
 ### Fixed — the live-DB `meta migrate` path now advances the committed snapshot
 

bun.lock

@@ -1,6 +1,6 @@
 {
   "name": "@metaobjectsdev/react",
-  "version": "0.20.13",
+  "version": "0.20.14",
   "description": "React runtime for metaobjects: useEntityForm hook and CurrencyInput component.",
   "type": "module",
   "main": "./dist/index.js",

client/web/packages/react/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metaobjectsdev/runtime-web",
-  "version": "0.20.13",
+  "version": "0.20.14",
   "description": "Pure framework-agnostic browser core for metaobjects: currency, filter URL serialization, fetcher contract types.",
   "type": "module",
   "main": "./dist/index.js",

client/web/packages/runtime-web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metaobjectsdev/tanstack",
-  "version": "0.20.13",
+  "version": "0.20.14",
   "description": "TanStack runtime for metaobjects: EntityFetcherProvider, EntityGrid, default cell renderers.",
   "type": "module",
   "main": "./dist/index.js",

client/web/packages/tanstack/package.json

@@ -13,9 +13,12 @@
 > - **NuGet** → keyless OIDC via the `publish-csharp.yml` workflow: `gh workflow run
 >   publish-csharp.yml` (or push a `csharp-v<version>` tag).
 >
-> Run network commands via the sandbox-disabled shell. Versions are **not unified** (TS/C#/Python
-> on the `0.x` line, Java/Kotlin on the `7.x` line). The rest of this doc is the per-registry
-> procedure.
+> Run network commands via the sandbox-disabled shell. **Single shared patch number (standing
+> policy since 0.20.13):** every release cuts ALL FOUR registries at the same `minor.patch` —
+> npm / PyPI / NuGet on `0.<m>.<p>`, Maven on `7.<m>.<p>` (only the major differs, for historical
+> continuity). A registry with no changed product file publishes a **version-parity bump**
+> (identical content at the new version) rather than sitting the release out. The rest of this doc
+> is the per-registry procedure.
 
 ## Releasing the TypeScript packages to npm
 
@@ -97,7 +100,7 @@ bytes**, not "did output change."
 | New **opt-in** codegen feature, default output byte-identical | new generator defaulting off | PATCH (MINOR if it adds registry vocabulary — cross-port conformance surface) | MINOR |
 | Wire-contract / conformance behavior change of already-valid deployments | FR-036 enforcement | **MINOR**, loud notice (pre-1.0 MINOR *is* the breaking slot) | MAJOR |
 | Wire behavior fixed to match the documented/conformance contract | 0.19.1 `@min` clamp | PATCH | PATCH |
-| Docs / tests / fixtures only (no product file in a port) | 0.19.4 npm scope | **No release for that registry** (per-registry scoping) | same |
+| No changed product file in a port | PyPI/NuGet/Maven at 0.20.14 | **Version-parity bump at the shared patch number** — publish identical content at the new version; never skip a registry (single-shared-patch policy, standing since 0.20.13) | same |
 
 **The `extStyle` 0.20.0 case, for calibration:** it was correctly MINOR — but for the
 *API break* (`relativeModuleSpecifier` gained a required param — a public export) **and**
@@ -210,7 +213,7 @@ How to publish the `MetaObjects*` C# packages to nuget.org. We use **Trusted Pub
 
 ## What gets published
 
-Four packages, version-locked at the C# port version (currently `0.19.7`):
+Four packages, version-locked at the C# port version (currently `0.20.13`):
 
 | Package | Contents |
 |---|---|
@@ -298,7 +301,7 @@ How to publish the **`metaobjects`** Python package to PyPI via **Trusted Publis
 ## What gets published
 
 One package, `metaobjects` (version in [`server/python/pyproject.toml`](../server/python/pyproject.toml),
-currently `0.19.9`), as an **sdist + a universal `py3-none-any` wheel** (pure Python).
+currently `0.20.13`), as an **sdist + a universal `py3-none-any` wheel** (pure Python).
 
 ## How we publish: Trusted Publishing (OIDC)
 
@@ -354,7 +357,7 @@ subsequent releases keyless.)
 # Releasing the Java/Kotlin modules to Maven Central
 
 The 18 `com.metaobjects:*` modules ship to **Maven Central via the Sonatype Central Portal**,
-versioned on the `7.x` line (currently `7.11.7`) in the parent + module poms. Signed with the
+versioned on the `7.x` line (currently `7.20.13`) in the parent + module poms. Signed with the
 maintainer's GPG key.
 
 ## Procedure
@@ -396,8 +399,10 @@ maintainer's GPG key.
 > If all are `200`, the release is out — the error was just the response parse. Bump the plugin to
 > ≥`0.7.0` to stop the crash on the next release.
 
-**Versions are not unified across languages** — TS, C#, and Python are on the `0.9.x` line, the
-Java/Kotlin module line is on the `7.2.x` track. Don't force one number. The cross-language contract
+**The `minor.patch` IS unified across languages** (standing policy since 0.20.13): npm, PyPI and
+NuGet share `0.<m>.<p>`, and Maven Central ships the same `minor.patch` on its historical major `7`.
+Every release bumps all four registries, with version-parity bumps where a port has no changed
+file. The cross-language *behavior* contract
 is the **conformance corpus + [`fixtures/conformance/CAPABILITIES.json`](../fixtures/conformance/CAPABILITIES.json)**:
 each release states which capabilities/conformance level it satisfies, and *that* manifest — not a
 shared version — is the coordination point. (Generated code runs without any MetaObjects runtime, so

docs/RELEASING.md

@@ -8,7 +8,7 @@
   -->
 
   <PropertyGroup>
-    <Version>0.20.13</Version>
+    <Version>0.20.14</Version>
     <Authors>Doug Mealing</Authors>
     <Company>Doug Mealing LLC</Company>
     <Product>MetaObjects</Product>

server/csharp/Directory.Build.props

@@ -6,7 +6,7 @@
     <parent>
         <groupId>com.metaobjects</groupId>
         <artifactId>metaobjects</artifactId>
-        <version>7.20.13</version>
+        <version>7.20.14</version>
     </parent>
 
     <artifactId>metaobjects-codegen-base</artifactId>

server/java/codegen-base/pom.xml

@@ -7,7 +7,7 @@
   <parent>
     <groupId>com.metaobjects</groupId>
     <artifactId>metaobjects</artifactId>
-    <version>7.20.13</version>
+    <version>7.20.14</version>
   </parent>
 
   <artifactId>metaobjects-codegen-kotlin</artifactId>

server/java/codegen-kotlin/pom.xml

@@ -6,7 +6,7 @@
     <parent>
         <groupId>com.metaobjects</groupId>
         <artifactId>metaobjects</artifactId>
-        <version>7.20.13</version>
+        <version>7.20.14</version>
     </parent>
 
     <artifactId>metaobjects-codegen-mustache</artifactId>