1.0.0-rc.8 — one advisory, added because two adopters shipped the same defect
Pre-release
1.0.0-rc.8 — one advisory, added because two adopters shipped the same defect
Cut from 645119b. The tree at this commit reads 0.25.0 / 7.25.0: a pre-release
version is never committed (scripts/check-no-prerelease-versions.sh), so this
annotation is the only record of what shipped.
npm 1.0.0-rc.8 (14 packages, dist-tag next)
PyPI — sat this one out (still 1.0.0rc6)
NuGet — sat this one out (still 1.0.0-rc.6)
Maven Central — sat this one out (still 8.0.0-rc.6)
metamodelVersion 1.0 — unchanged; no registered vocabulary moved.
Why three registries sat it out: identical to rc.7's reasoning. The single commit
since rc.7 is confined to @metaobjectsdev/cli. docs/RELEASING.md's convergent-
publishing rule keeps a port at its current version until it has a changed product
file, and the override (a change to expected-registry.json or metamodelVersion)
does not fire.
Why this RC exists. The nine-estate round on rc.7 was clean, and it surfaced one
defect that was not in the product and not in any gate: TWO of the nine adopters
had shipped <EntityFetcherProvider value={f}> — the prop 1.0 renamed to
fetcher. It does not typecheck, and both the migration note and the F52 base-URL
advisory rest a safety argument on that. The argument holds only where tsc is in
the gate chain, and in neither estate was it: vite build transpiles without
typechecking, and a provider with the wrong prop still RENDERS, so nothing fails
until a component calls a generated hook in a browser and finds no fetcher. One
adopter lost a round reading that as the candidate breaking; the second carried it
through a whole upgrade pass past its drift gates, unit tests and build.
meta verify now names it. Warning only — it never touches the exit code, because
the scan cannot see a re-export or an aliased local component. Unlike the base-URL
advisory it fires at ANY apiPrefix: no configuration exists under which the old
prop reaches the provider.
The maintainer ruled that this rides an RC rather than going straight into 1.0, so
the estates run the bits that become the release rather than one commit behind them.