release: 0.10.1#1096
Merged
Merged
Conversation
Resolves the port-parity gap (#1090): the Compose FieldView took a single accent and drew every particle from it, collapsing a multi-colour field to one hue, where the JS and Swift engines' FieldOptions already carried a palette. Adds palette: List<Color>, colouring each particle by a stable pool index across all four render modes. Backward-compatible — defaults to [accent], so existing callers are unaffected. Verified against the iOS 10-intro-star, which the Android field now matches. Kotlin-only change. JS and Swift are byte-identical to 0.10.0; npm and Swift republish at 0.10.1 solely to hold the cross-plane version in lockstep. No JS or Swift behaviour changed, and the changelog says so explicitly so nobody reads a JS change into the bump. Seven packages + FIELD_VERSION at 0.10.1 in lockstep. The version bump used the corrected ./packages/* filter (from #1094) — verified the three private apps were NOT bumped this time (site 0.2.0, starter 0.1.0, observatory 0.0.0 unchanged). #1091 (parity matrix doesn't track colour) stays open — it is why this reached an app before a gate; closing it makes a future palette divergence a CI failure. typecheck, build, check:api, check:docs, check:links, FIELD_VERSION lockstep — all green.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Kotlin port parity — the Compose
FieldViewrenders a multi-hue palette. Resolves #1090; ships the fix merged in #1095.What & scope
FieldViewgainspalette: List<Color>(backward-compatible; defaults to[accent]). Each particle takes a stable colour by pool index across all four render modes. Verified against the iOS10-intro-star.Versions
FIELD_VERSION→0.10.1(lockstep, drift test green)../packages/*filter from release: scope the version bump to publishable packages, not the name glob #1094 held: site/starter/observatory unchanged at 0.2.0 / 0.1.0 / 0.0.0.Release
git tag v0.10.1→ npm + Swift (SPM) + Kotlin (Maven, via the CI job) in lockstep. Ascent then flips0.10.1-local→0.10.1.Still open
#1091 — the parity matrix doesn't track colour, which is why this reached an app before a gate. Closing it makes a future palette divergence fail CI instead of shipping.
Gates
typecheck · build ·
check:api(no removals) ·check:docs·check:links· FIELD_VERSION lockstep — all green.