Skip to content

chore(release): prepare CeraUI 2026.10.0 - #404

Merged
andrescera merged 3 commits into
mainfrom
chore/release-prep-2026.10.0
Oct 24, 2026
Merged

andrescera merged 3 commits into
mainfrom
chore/release-prep-2026.10.0

Conversation

@andrescera

@andrescera andrescera commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

What

Prepares the CeraUI version for the next stable release: the root package.json version becomes 2026.10.0, and the federation build document whose current-version example is enforced by a contract test is updated. The other fifteen 2026.9.5 literals (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 unless package.json has exactly that version.

How to verify

  • jq -r .version package.json prints 2026.10.0.
  • bash scripts/build/deb-version-stamp.test.sh passes: 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 and documentation-contract.test.mjs).
  • Re-derive the calculated version right before dispatch with the release runbook's predictor.

Risks

  • Valid for a dispatch until 2026-10-31T23:59:59Z (the workflow uses the runner's UTC date; that is 18:59:59 at UTC-5). After that it calculates 2026.11.0 and this change must be redone with a new review.
  • Re-predict even within October if any v2026.10.* tag appears, and leave force_version unset (never use it to rescue this change).
  • Merge it last, immediately before the dispatch, because it changes what the main build produces; require a green Build Check on the merge ref or on the post-merge main push before dispatching.

@coderabbitai

coderabbitai Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f0b5431f-034b-4df2-a6b4-340972984099

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@andrescera
andrescera merged commit 7c076c1 into main Oct 24, 2026
18 checks passed
@andrescera
andrescera deleted the chore/release-prep-2026.10.0 branch October 24, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant