Skip to content

chore(deps): bump changesets/action from 1.9.0 to 2.1.2 #459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): bump changesets/action from 1.9.0 to 2.1.2 #459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/changeset.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ jobs:

- name: Create Release Pull Request or Publish to npm
id: changesets
uses: changesets/action@a45c4d594aa4e2c509dc14a9f2b3b67ba3780d0d # v1.9.0
uses: changesets/action@ae32849d5ba541f9ae29e40e22a623bc13562f51 # v2.1.2

@devin-ai-integration devin-ai-integration Bot Sep 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 CLI mismatch blocks all releases

Every run fails before mode selection because changesets/action@v2 rejects Changesets CLI 2.29.8. The dependency declaration pins that version. Version pull requests and npm releases stop.

Learn more

The v2 action validates the installed Changesets CLI before reading inputs or selecting versioning versus publishing. Its compatibility check rejects any CLI major version 2, while this repository installs @changesets/cli 2.29.8 through the dependency declaration. Therefore every push to a configured release branch fails before either release path starts.

Example: Merging a user change with a changeset into main starts the Release workflow. The action detects CLI 2.29.8 and exits with its v3 compatibility error instead of opening the Version Packages pull request.

Recommended fix: Upgrade @changesets/cli and the lockfile to a compatible v3 release, then verify ci:version, ci:publish, and the Changesets configuration against v3. Otherwise keep changesets/action on v1.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@devin-ai-integration devin-ai-integration Bot Sep 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Legacy inputs abort releases

After CLI validation succeeds, changesets/action@v2 rejects the configured version and publish inputs. Version pull requests and npm publishing never run.

Learn more

The v2 root action treats the v1 input names as configuration errors. This workflow still passes version and publish, so execution throws before reading their commands. The current CLI incompatibility fails first, but correcting that dependency exposes this independent failure.

Example: With Changesets CLI v3 installed, a push to main reaches the action. It reports that version and publish were renamed, then exits without running yarn ci:version or yarn ci:publish.

Recommended fix: Rename version to version-script and publish to publish-script. Exercise both a changeset-bearing commit and a merged version pull request to validate the two release modes.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

with:
version: yarn ci:version
publish: yarn ci:publish
Expand Down
Loading