Repository navigation
chore(deps): update changesets/action action to v2 - #29
renovate-appwrite[bot] wants to merge 1 commit into
Conversation
🔵 Tier A · Mergeable after minor fixes
The version workflow upgrades its Changesets action reference from the v1 tag to the pinned v2.1.2 commit.
Note Not approving while a bug finding is open: Rename the inputs for changesets/action v2
Fix with agent prompt### Issue 1
.github/workflows/version.yml:42
**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.📂 Walkthrough · 1
Reviewed |
| # 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 |
There was a problem hiding this 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.
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.
This PR contains the following updates:
v1→v2.1.2Release Notes
changesets/action
v2.1.2Compare Source
Patch Changes
#735
8833883Thanks @bluwy! - Handle error when pushing git tags with the git CLI#724
36f529fThanks @bluwy! - Improve log messages#724
36f529fThanks @bluwy! - Fix root action double error logs#729
ca85897Thanks @bluwy! - Always switch and reset branch when generating version commits, similar to ifpush-with-git-cliis enabledv2.1.1Compare Source
Patch Changes
da1ea29Thanks @KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2v2.1.0Compare Source
Minor Changes
3b7c71cThanks @bluwy! - Add acwdinput to the root action,/select-mode,/version,/pack, and/publishsub-actions to set the current working directory to execute Changesets in. This input existed in v1 but was incorrectly removed.Patch Changes
6f58ba3Thanks @bluwy! - Updatepr-statusmessage to link to the new faq pagev2.0.0Compare Source
Major Changes
#692
cb3f011Thanks @Andarist! - Release commits and tags are now pushed using the GitHub API by default.Replace the
commit-modeinput with the booleanpush-with-git-cliinput. Setpush-with-git-cli: trueto continue using the Git CLI.Regardless of the push mode, custom GitHub tokens must be passed explicitly through the
github-tokeninput. TheGITHUB_TOKENenvironment variable and credentials configured byactions/checkoutor embedded in remote URLs are not substitutes for this input. When the Git CLI is enabled,github-tokentakes precedence over those repository credentials.#680
ca57073Thanks @bluwy! - Add a newpush-git-tagsoption that complementscreate-github-releasesto control specifically if git tags should be created but not GitHub releases.If
create-github-releaseswas previously set tofalse, which also indirectly disabled git tag creation, git tags will now be created instead by default. If this is not desired, setpush-git-tagstofalseexplicitly.#657
4f718b5Thanks @Andarist! - Removed compatibility support for old Changesets v1.#681
7359107Thanks @bluwy! - Rename the root action inputs and outputs to better match the sub-actions' conventions.Inputs:
version->version-scriptpublish->publish-scriptcommit->commit-messagetitle->pr-titlebranch->pr-base-branchOutputs:
pull-request-number->pr-number#674
164652bThanks @bluwy! - Remove support for passing custom GitHub token through the GITHUB_TOKEN environment variable. It should be passed to thegithub-tokeninput instead.#659
5649ff4Thanks @bluwy! - Removecwdoption forchangesets/action. Use the stepworking-directoryoption instead to change the directory.#673
823cf74Thanks @bluwy! - Update to Changesets v3 packages#695
469993cThanks @bluwy! - Removed.npmrchandling when theNPM_TOKENenvironment variable is set.Authentication should be handled via Trusted Publishing instead. If a token is still needed, use
actions/setup-nodeto set it up instead via theregistry-urloption. Check out the updated action README for more information of setting up npm authentication in GitHub Actions.#668
0eae789Thanks @bluwy! - Rename the input and output names to kebab-case instead of camelCase to match the official GitHub actions patternMinor Changes
#656
a12d90dThanks @bluwy! - Add new/select-mode,/version, and/publishsub-actions to better control version and publish steps#678
f71ae04Thanks @Andarist! - Published packages detection done through stdout parsing was replaced with one based on the shared output file usingCHANGESETS_OUTPUTenvironment variable. When using custom scripts this environment variable should always be passed down to the Changesets CLI invocations.Patch Changes
#699
5b307d3Thanks @Andarist! - Validate that projects use Changesets CLI v3 and direct Changesets CLI v2 users tochangesets/action@v1.#697
84d78c6Thanks @Andarist! - Allow custom publish scripts to complete without a Changesets output file, warning that GitHub releases and git tags cannot be created when that file is missing.#670
5a8b9b7Thanks @Andarist! - Authenticate git CLI pushes with the configured GitHub token using Git extra headers instead of writing to a global.netrcfile.#670
5a8b9b7Thanks @Andarist! - Derive the Git server URL from the GitHub Actions context when configuring git CLI authentication to support GitHub Enterprise Server setups.#688
219ea82Thanks @Andarist! - Remove thesetup-git-userinput. Complete custom Git identities are now preserved automatically, whilegithub-actions[bot]is configured as a fallback before creating local release commits or tags.Configuration
📅 Schedule: (UTC)
* * * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.