diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 708398f..9926cd5 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -29,10 +29,10 @@ jobs:
       - run: node scripts/assert-publishable.ts
       # Keep the maintained Changesets 2 npm publisher: v3 selects Yarn, whose bundled
       # provenance client fails this release with a duplicate transparency-log entry.
-      - uses: changesets/action@66d7d1ddafddf1ef45f98ee51a7496f9cdadb2f4 # v2.1.2
+      - uses: changesets/action@a45c4d594aa4e2c509dc14a9f2b3b67ba3780d0d # v1.9.0; CLI 2-compatible
         with:
-          version-script: corepack yarn changeset version
-          publish-script: corepack yarn changeset publish
+          version: corepack yarn changeset version
+          publish: corepack yarn changeset publish
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_CONFIG_PROVENANCE: "true"
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0323f08..ed3ecc0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -314,7 +314,7 @@ yarn changeset
 3. The Changesets workflow will open a “Version Packages” PR.
 4. Merge that PR to publish to npm and tag the release.
 
-Yarn installs and builds the project. Changesets is pinned to the maintained 2.x publisher so
+Yarn installs and builds the project. Changesets CLI 2 and its compatible Action 1 are pinned so
 the release uses npm's trusted-publishing/OIDC and provenance support. Changesets 3 switches a
 Yarn workspace to Yarn's publisher; do not upgrade it until that path passes publication with
 provenance enabled. The 0.6.1 release hit a duplicate transparency-log entry in that path.