From aac9fb9bf9d36dd47c9bb05b6bacbc84953491cd Mon Sep 17 00:00:00 2001 From: ru44 <18311071+ru44@users.noreply.github.com> Date: Sat, 10 Oct 2026 21:33:13 +0300 Subject: [PATCH] ci: publish with changesets/action v2 so releases get tags again @changesets/cli v3 no longer prints the "New tag:" lines that changesets/action v1 parsed, so the 2.2.0 run published to npm but skipped the git tag and GitHub release (both were created by hand afterwards). Action v2 reads the CHANGESETS_OUTPUT file instead and renames the inputs to version-script, publish-script and github-token (which defaults to the workflow token). --- .github/workflows/publish.yml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index c34bf2d..295b42f 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -48,11 +48,13 @@ jobs: # with no pending release is a no-op instead of re-publishing the current version. # Auth is via OIDC (configure the trusted publisher for `cliuno` on npmjs.com); # no NPM_TOKEN secret is required. + # changesets/action v2 is the release line for @changesets/cli v3: it reads what was + # published from the CHANGESETS_OUTPUT file, which `changeset publish` inside + # ci-publish.sh writes. v1 parsed CLI v2's "New tag:" stdout, which v3 no longer prints, + # so it published to npm but skipped the git tag and GitHub release. - name: Create Release Pull Request or Publish id: changesets - uses: changesets/action@v1 + uses: changesets/action@v2 with: - version: pnpm changeset:version - publish: bash scripts/ci-publish.sh - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + version-script: pnpm changeset:version + publish-script: bash scripts/ci-publish.sh