Skip to content
Open
Changes from all commits
Commits
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/version.yml
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ jobs:
# here: merging that pull request and publishing a GitHub Release for the
# new tag is what ships to npm, via release.yml.
- name: Create or update the version pull request
uses: changesets/action@v1
uses: changesets/action@ae32849d5ba541f9ae29e40e22a623bc13562f51 # v2.1.2

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Rename the inputs for changesets/action v2

In v2, the root inputs are version-script, pr-title, and commit-message, so the existing version, title, and commit entries are ignored. The version command falls back to changeset version, but the generated version PR and commit will use the default Version Packages instead of the configured chore: version packages.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/version.yml
Line: 42

Comment:
**Rename the inputs for changesets/action v2**

In v2, the root inputs are `version-script`, `pr-title`, and `commit-message`, so the existing `version`, `title`, and `commit` entries are ignored. The version command falls back to `changeset version`, but the generated version PR and commit will use the default `Version Packages` instead of the configured `chore: version packages`.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

with:
version: npm run version
title: 'chore: version packages'
Expand Down
Loading