Skip to content

chore(deps): bump changesets/action from 1.9.0 to 2.1.1 #452

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
+1 −1
Open

chore(deps): bump changesets/action from 1.9.0 to 2.1.1 #452

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@8488615a623b1b9c987934bb89eae8af6a946ac1 # v2.1.1

@devin-ai-integration devin-ai-integration Bot Aug 28, 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.

🔴 Release action ignores renamed version and publish inputs

changesets/action v2 renamed the version and publish inputs to version-script and publish-script. The upgraded step still passes the old names (version/publish), so both are ignored and the custom yarn ci:version and yarn ci:publish scripts never run.

Prompt for agents 
changesets/action was bumped from v1.9.0 to v2.1.1. In v2.0.0 the root action inputs were renamed: `version` -> `version-script` and `publish` -> `publish-script`. The workflow step at .github/workflows/changeset.yaml still uses the old input names `version:` and `publish:` under `with:`. Rename them to `version-script:` and `publish-script:` respectively so the custom ci:version and ci:publish scripts are used.
Devin Review

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

@devin-ai-integration devin-ai-integration Bot Aug 28, 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.

🔴 Release token passed only through unsupported env var

changesets/action v2 dropped reading the token from the GITHUB_TOKEN environment variable and requires the github-token input instead. The step still supplies the token only via env.GITHUB_TOKEN, leaving the action without credentials to create the release PR or publish.

Prompt for agents 
changesets/action v2.0.0 removed support for passing a custom GitHub token through the GITHUB_TOKEN environment variable; the token must now be passed through the `github-token` input. The workflow step in .github/workflows/changeset.yaml only sets `env.GITHUB_TOKEN`. Add `github-token: ${{ secrets.GITHUB_TOKEN }}` under the `with:` block so the action can authenticate.
Devin Review

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

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