Fix package scope in backported changeset - #6332
Merged
Merged
Conversation
The changeset was backported from a branch where the packages are published under the @dextinity/* scope. On v8.x.x they still use @comet/*, so Changesets aborts while assembling the release plan and no release can be published. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017d1A8MxYTpS29HTXgKJpJA
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 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 |
VPS-Obi
approved these changes
Sep 8, 2026
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.
Problem
The release workflow on
v8.x.xfails when assembling the release plan:No release can be published from
v8.x.xuntil this is resolved.Cause
.changeset/user-permissions-wildcard-content-scope.mdwas backported from a branch where the packages are already published under the@dextinity/*scope. Onv8.x.xthey still use@comet/*, so@dextinity/cms-apidoes not exist in the workspace and Changesets aborts.This is the second time the same mistake blocks the v8 release, and it happened despite the backport routine explicitly warning about it. #6293 fixed the identical break for
olive-pears-inventless than a week ago. The routine carries a caveat about adjusting the changeset scope when backporting tov8.x.x— #6318 followed it and renamed its changeset, but #6292, which added this one, did not. A caveat in the prompt is evidently not enough: the routine needs a check that fails the backport when a changeset names a package that isn't in the target branch's workspace.Fix
Rename the packages in the changeset's frontmatter to
@comet/cms-apiand@comet/cms-admin, matching the names inpackages/api/cms-api/package.jsonandpackages/admin/cms-admin/package.jsonon this branch. The changeset text is unchanged, so the released changelog entry stays the same.Verification
changeset statuscannot run on this branch (it resolves changed packages against amainbase ref that doesn't apply here), so the release plan was assembled directly via@changesets/get-release-plan. It now succeeds and versions 19 packages from8.31.0to8.32.0, consuming both pending changesets.Further information
🤖 Generated with Claude Code
https://claude.ai/code/session_017d1A8MxYTpS29HTXgKJpJA
Generated by Claude Code