release: 0.10.0#1093
Conversation
Ships FieldHandle.guarantees and completes cross-plane publishing. Breaking (pre-1.0): FieldHandle gains a required 'guarantees' member. Additive for every consumer — reading field.guarantees breaks no calling code — and breaking only for third-party code that implements FieldHandle itself, which must now provide the member. Migration: return the runtime envelope or delegate to a wrapped field; the in-repo implementers FieldLayer and FieldField both delegate and are the reference pattern. A break to a protected symbol is the 0.MINOR position pre-1.0, hence 0.10.0 not a patch. All seven packages bumped to 0.10.0 together; FIELD_VERSION advanced in lockstep across the JS, Swift and Kotlin planes (drift test green). CHANGELOG restructured into a dated [0.10.0] section with the breaking change and its migration called out first, so release.yml renders a correct GitHub release body. Revived the per-version release note at docs/release-notes/0.10.0.md. Corrected two stale version strings the drift had left behind — PUBLISHING.md said 0.9.2, the README citation said 0.9.3. One git tag v0.10.0 now releases npm, Swift (SPM tag) and Kotlin (Maven, via the CI publish job added in #1089) at a single version. typecheck, build, check:api (20 protected, no removals), check:docs, check:links and the full suite all green.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3fb0f33ae6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "@fundamental-engine/create", | ||
| "version": "0.9.5", | ||
| "version": "0.10.0", |
There was a problem hiding this comment.
When publishing @fundamental-engine/create as 0.10.0, the bundled templates under packages/create/templates still depend on @fundamental-engine/{vanilla,react,elements} as ^0.9.2; for 0.x semver that range is <0.10.0. In the npm create @fundamental-engine@latest flow, a freshly scaffolded app will therefore install the previous 0.9.x runtime even though the CLI reports 0.10.0, missing new 0.10 surface such as field.guarantees; update those template ranges (or intentionally exact-pin 0.10.0) with the release bump.
Useful? React with 👍 / 👎.
1 participant
Ships
FieldHandle.guaranteesand completes cross-plane publishing. The major we deferredguaranteesfor.Breaking (pre-1.0)
FieldHandlegains a requiredguaranteesmember.field.guaranteesbreaks no calling code.FieldHandle— it must now provide the member.FieldLayer(@fundamental-engine/three) andFieldField(@fundamental-engine/vanilla) both delegate and are the reference pattern.A break to a protected symbol is the
0.MINORposition pre-1.0 →0.10.0, not a patch.Versions
0.10.0together. The three private apps (site, starter, observatory) stay at their independent versions — the@fundamental-engine/*bump initially swept them in; reverted.FIELD_VERSION→0.10.0in lockstep across JS, Swift, Kotlin (drift test green).Cross-plane release
One
git tag v0.10.0now publishes every plane at one version:Docs
[0.10.0]with the breaking change + migration first, sorelease.ymlrenders a correct GitHub release body.docs/release-notes/0.10.0.md.PUBLISHING.md(0.9.2) and the README citation (0.9.3).Gates
typecheck · build ·
check:api(20 protected, no removals —guaranteesis additive at the symbol level) ·check:docs·check:links· full suite · FIELD_VERSION lockstep — all green. Publish config verified against local Maven before the Android infra merged.