Repository navigation
chore(release): prepare CeraUI 2026.10.0 - #404
Merged
Merged
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
What
Prepares the CeraUI version for the next stable release: the root
package.jsonversion becomes2026.10.0, and the federation build document whose current-version example is enforced by a contract test is updated. The other fifteen2026.9.5literals (history, fixtures, previous-version upgrade arguments) are deliberately unchanged. No workflow, dependency, lockfile, workspace-package version or build implementation changes.Why
The publish-release workflow calculates the next stable version from the current UTC date and the existing tags (predicted
2026.10.0) and refuses to run unlesspackage.jsonhas exactly that version.How to verify
jq -r .version package.jsonprints2026.10.0.bash scripts/build/deb-version-stamp.test.shpasses: it proves the package build stamps<package.json version>-<UTC stamp>.<checkout SHA>(the value itself is enforced by the workflow's two equality gates anddocumentation-contract.test.mjs).Risks
2026.11.0and this change must be redone with a new review.v2026.10.*tag appears, and leaveforce_versionunset (never use it to rescue this change).mainpush before dispatching.