versioned_docs_archived/version-9.x/using-changesets.md
:::note
At the time of writing this documentation, the latest pnpm version was v6.14. The latest Changesets version was v2.16.0.
:::
To setup changesets on a pnpm workspace, install changesets as a dev dependency in the root of the workspace:
pnpm add -Dw @changesets/cli
Then changesets' init command:
pnpm changeset init
To generate a new changeset, run pnpm changeset in the root of the repository.
The generated markdown files in the .changeset directory should be committed
to the repository.
pnpm changeset version. This will bump the versions of the packages
previously specified with pnpm changeset (and any dependents of those) and
update the changelog files.pnpm install. This will update the lockfile and rebuild packages.pnpm publish -r. This command will publish all packages that have
bumped versions not yet present in the registry.To automate the process, you can use changeset version with GitHub actions.
The action will detect when changeset files arrive in the main branch, and then open a new PR listing all the packages with bumped versions. Once merged, the packages will be updated and you can decide whether to publish or not by adding the publish property.
Add a new script ci:publish which executes pnpm publish -r.
It will publish to the registry once the PR is opened by changeset version.
package.json
{
"scripts": {
"ci:publish": "pnpm publish -r"
},
...
}
name: Changesets
on:
push:
branches:
- main
env:
CI: true
PNPM_CACHE_FOLDER: .pnpm-store
jobs:
version:
timeout-minutes: 15
runs-on: ubuntu-latest
steps:
- name: checkout code repository
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: setup node.js
uses: actions/setup-node@v3
with:
node-version: 14
- name: install pnpm
run: npm i pnpm@latest -g
- name: Setup npmrc
run: echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > .npmrc
- name: setup pnpm config
run: pnpm config set store-dir $PNPM_CACHE_FOLDER
- name: install dependencies
run: pnpm install
- name: create and publish versions
uses: changesets/action@v1
with:
version: pnpm ci:version
commit: "chore: update versions"
title: "chore: update versions"
publish: pnpm ci:publish
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
More info and documentation regarding this action can be found here.