Repository navigation
ci(release): bump every v2 package together via fixed versioning - #1042
Open
taylanpince wants to merge 1 commit into
Open
taylanpince wants to merge 1 commit into
taylanpince wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
`linked` only aligns versions among packages that are already being bumped, so the 2.3.48 release left core and other untouched packages at 2.3.47. `update-version` reads core's version, so VERSION (sent by the provider as clientVersion) would have stayed at 2.3.47 while the provider shipped as 2.3.48. Switch to `fixed` and include the unscoped `0xsequence` package so any changeset releases every package at one version, as PUBLISHING.md describes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
taylanpince
force-pushed
the
ci/v2-fixed-versions
branch
from
October 20, 2026 21:42
7888803 to
ef69784
Compare
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.
Summary
Addresses the Codex finding on #1037: that release bumps only the packages reached by changesets (and their dependents) to 2.3.48, leaving
@0xsequence/coreand others at 2.3.47. Becauseupdate-versionembeds core's version,VERSION(sent by the provider asclientVersion) would report 2.3.47 from a 2.3.48 provider, and the release would not match thePUBLISHING.mdclaim that every package is staged at one version..changeset/config.json: replacelinkedwithfixed: [["@0xsequence/*", "0xsequence"]].linkedonly aligns versions among packages already being bumped;fixedbumps the whole group on any changeset. The unscoped0xsequencepackage is listed explicitly since the glob does not match it.PUBLISHING.md: describe the fixed versioning accurately.Test plan
pnpm changeset status --verboseon this branch lists all 25 packages (including@0xsequence/core) at 2.3.48.VERSION = '2.3.48'.🤖 Generated with Claude Code