From 243db1d7cc80519f611623774466f64d59873fce Mon Sep 17 00:00:00 2001 From: Toti Date: Sun, 30 Aug 2026 07:41:34 -0300 Subject: [PATCH] chore(deps): bump changesets/action from 1 to 2 v2 no longer accepts the GitHub credential from the GITHUB_TOKEN environment variable or from the remote that actions/checkout configures; it must arrive as the github-token input. Without it the action cannot open the release PR or push tags, and CI would not have caught it -- nothing in the test matrix exercises the release workflow. Release commits and tags now go through the GitHub API rather than the git CLI, which is v2's default and needs no configuration here. The commit-mode input this repo never set is the one that was replaced. --- .github/workflows/release.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index da9f643..72cd2f7 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -38,12 +38,18 @@ jobs: run: pnpm build - name: Create release PR or publish - uses: changesets/action@v1 + uses: changesets/action@v2 with: publish: pnpm release version: pnpm changeset version commit: "chore: version packages" title: "chore: version packages" + # v2 requires the GitHub credential as an explicit input. It no + # longer accepts the GITHUB_TOKEN environment variable, nor the + # credentials actions/checkout leaves in the git remote, so + # without this line the action cannot open the release PR or push + # tags. The env entry below stays for the changesets CLI itself. + github-token: ${{ secrets.GITHUB_TOKEN }} env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Two different consumers read the npm credential, under two different