chore(release): prepare 26.10.3 - #125
Merged
Merged
Conversation
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
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.
Prepare @mivabyte/ui 26.10.3 with the exact cyan and warm apricot palette. Consume pending Changesets, consolidate the superseded cyan-ramp notes into the final palette entry, and synchronize the package and lockfile versions.
Release checks exposed a shared-build race: the dry-run packaging test could invoke prepare while other tests imported dist. Pack an isolated fixture instead. Update 12 Linux Chromium baselines from the CI renderings for the intentional button and selection changes; initial and retry images were byte-identical.
Validation: npm run verify passes locally on Node 22, including package contracts, packed consumer types and runtime coverage. Linux browser and Node 22/24 checks run on this PR before publishing.
This is version preparation plus test maintenance; the package-facing palette changes are already on main and their release intent is consumed here.