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
2 changes: 1 addition & 1 deletion .changeset/config.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"$schema": "https://unpkg.com/@changesets/config@3.0.0/schema.json",
"$schema": "https://unpkg.com/@changesets/config@4.0.0/schema.json",
"changelog": "@changesets/cli/changelog",
"commit": false,
"fixed": [],
Expand Down
12 changes: 6 additions & 6 deletions .github/workflows/release-reusable.yml
Original file line number Diff line number Diff line change
Expand Up @@ -84,12 +84,12 @@ jobs:
# points at this repo's release.yml workflow, and npm must be >= 11.5.1
# (satisfied by the Node version in .node-version).
- name: Create release PR or publish
uses: changesets/action@a45c4d594aa4e2c509dc14a9f2b3b67ba3780d0d # v1.9.0
uses: changesets/action@8488615a623b1b9c987934bb89eae8af6a946ac1 # v2.1.1
with:
publish: pnpm release
version: pnpm version-packages
commit: 'Release new artifacts'
title: 'Release new artifacts'
github-token: ${{ steps.app-token.outputs.token }}
publish-script: pnpm release
version-script: pnpm version-packages
commit-message: 'Release new artifacts'
pr-title: 'Release new artifacts'
env:
GITHUB_TOKEN: ${{ steps.app-token.outputs.token }}
NPM_CONFIG_PROVENANCE: ${{ inputs.provenance }}
6 changes: 5 additions & 1 deletion CONSUMING.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Consumers call the reusable workflow `release-reusable.yml`. `release.yml` in th

Publishing uses **npm Trusted Publishing** (OIDC): the workflow exchanges the job's `id-token` for a short-lived npmjs.org credential and npm signs **provenance** automatically. No npm token is stored or passed. Each published package needs a Trusted Publisher configured on npmjs.org (see Prerequisites).

If your `release` script only creates git tags (e.g. `changeset tag`) and never runs `npm publish`, none of the npm / Trusted-Publishing setup applies.
If your `release` script only creates git tags (e.g. `changeset git-tag`) and never runs `npm publish`, none of the npm / Trusted-Publishing setup applies.

```yaml
name: Release
Expand Down Expand Up @@ -107,7 +107,11 @@ jobs:

**Prerequisites:**

- Install `@changesets/cli@^3`. The reusable workflow uses
`changesets/action@v2`, which does not support Changesets CLI v2.
- Your `package.json` must define `release` and `version-packages` scripts.
Use `changeset publish` when publishing packages, or `changeset git-tag` for
a tag-only repository.
- The workflow uses a **GitHub App token** for all git operations. This ensures that tags pushed by the release workflow trigger downstream workflows (e.g. `deploy.yml`), which `GITHUB_TOKEN` cannot do.
- Create a GitHub App with `contents: write` and `pull-requests: write` permissions on your repository.
- Add `APP_ID` (the numeric App ID — used as `client-id`) and `APP_PRIVATE_KEY` (the PEM private key) as repository secrets.
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
"marketplace:check": "node scripts/sync-marketplace.mjs --check"
},
"devDependencies": {
"@changesets/cli": "^2.31.1",
"@changesets/cli": "^3.0.1",
"@kin0992/oxc-config": "workspace:*",
"oxfmt": "catalog:core",
"oxlint": "catalog:core",
Expand Down
Loading