release: 0.9.5#1084
Merged
Merged
Conversation
Seven published packages bumped together: core, create, dom, elements, react, three, vanilla. FIELD_VERSION bumped on all three planes (JS, Swift, Kotlin) to match, and the lockstep drift guard passes. The three private workspace apps are reverted rather than bumped. Note that this is now THREE, not two — apps/observatory was added this cycle and matches the @fundamental-engine/* filter, so the documented two-app revert step is out of date. RELEASING.md is updated accordingly in this commit. Patch, not minor: the protected-surface baseline was diffed across the whole cycle and no protected symbol was removed. Everything in this release is additive, internal, or documentation. The Swift and Kotlin constants were edited without a local toolchain to verify them; they are checked by their own planes' CI rather than by me. Today's work is JS-only, so those two bumps exist solely to hold lockstep. Full gate green on 1aec803: typecheck, build, test, check:api, check:dist, check:readme, check:recipes, check:cem, check:docs, check:links.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Patch, not minor — verified rather than assumed: the protected-surface baseline was diffed across the entire cycle and no protected symbol was removed. Everything in this release is additive, internal, or documentation.
Version moves
0.9.4→0.9.5(core, create, dom, elements, react, three, vanilla)FIELD_VERSIONsite0.2.0,starter0.1.0,observatory0.0.0)A correction to the procedure
RELEASING.mdsaid to revert two private apps. It is now three —apps/observatorywas added this cycle and matches the@fundamental-engine/*filter. Bumping it would have been harmless (it isprivate: true) but the checklist was already wrong and would have silently rotted further.The step is corrected and now tells you to confirm with a command rather than trust the list, since it grows whenever a private app is added.
What I could not verify
The Swift and Kotlin constants were edited without a local toolchain. They are checked by their own planes' CI, not by me. Today's work is JS-only, so those two bumps exist purely to hold lockstep — the ports have no functional change in this release.
Gates
Full gate green on
1aec803fbefore the bump, and re-run after: typecheck · build · test ·check:api·check:dist·check:readme·check:recipes·check:cem·check:docs·check:links· theFIELD_VERSIONlockstep drift guard.After merge
Tagging
v0.9.5triggers the release workflow, which re-runs the full gate and publishes all seven packages to npm with provenance. Nothing is published from a laptop.