Version Packages (next) (#664)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
changesets-org-version-bot[bot]
2026-06-23 11:29:25 +00:00
committed by GitHub
co-authored by github-actions[bot]
parent dc29b738b5
commit 0490518932
4 changed files with 24 additions and 7 deletions
+5 -5
View File
@@ -65,7 +65,7 @@ jobs:
run: pnpm install --frozen-lockfile
- name: Create Release Pull Request
uses: changesets/action@v1
uses: changesets/action@v2
```
#### With Publishing
@@ -103,7 +103,7 @@ jobs:
- name: Create Release Pull Request or Publish to npm
id: changesets
uses: changesets/action@v1
uses: changesets/action@v2
with:
# This expects you to have a script called release which does a build for your packages and calls changeset publish
publish: pnpm release
@@ -170,7 +170,7 @@ jobs:
- name: Create Release Pull Request or Publish to npm
id: changesets
uses: changesets/action@v1
uses: changesets/action@v2
- name: Publish
if: steps.changesets.outputs.hasChangesets == 'false'
@@ -214,7 +214,7 @@ jobs:
run: pnpm install --frozen-lockfile
- name: Create Release Pull Request
uses: changesets/action@v1
uses: changesets/action@v2
with:
# this expects you to have a npm script called version that runs some logic and then calls `changeset version`.
version: pnpm version
@@ -225,7 +225,7 @@ jobs:
If you are using [Yarn Plug'n'Play](https://yarnpkg.com/features/pnp), you should use a custom `version` command so that the action can resolve the `changeset` CLI:
```yaml
- uses: changesets/action@v1
- uses: changesets/action@v2
with:
version: yarn changeset version
# ...