Skip to content

Commit df226e9

Browse files
authored
docs: modify release steps (#598)
1 parent 9f9fa77 commit df226e9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -127,8 +127,8 @@ For VS Code users, you can install the [Biome VS Code extension](https://marketp
127127

128128
Repository maintainers can publish a new version of changed packages to npm.
129129

130-
1. Run `pnpm generate-release-pr` to generate a release branch.
131-
2. Create a pull request, the title should be `release: v1.2.0`.
132-
3. Run the [release action](https://github.com/web-infra-dev/rsbuild/actions/workflows/release.yml) to publish packages to npm.
133-
4. Generate the [release notes](https://github.com/web-infra-dev/rsbuild/releases) via GitHub, see [Automatically generated release notes](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes)
134-
5. Merge the release pull request to `main`.
130+
1. Run `pnpm generate-release-pr` to generate a release branch, the default bump type is `patch`, use `--type minor/major` to bump minor/major version.
131+
2. Create a pull request, the title should be `Release: v1.2.0`, ensure the CI check passes.
132+
3. Run the [release action](https://github.com/web-infra-dev/rslib/actions/workflows/release.yml) to publish packages to npm.
133+
4. Merge the release pull request to `main`.
134+
5. Generate the [release notes](https://github.com/web-infra-dev/rslib/releases) via GitHub, see [Automatically generated release notes](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes)

0 commit comments

Comments
 (0)