Skip to content
Merged
Show file tree
Hide file tree
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
6 changes: 3 additions & 3 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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"
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading