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
1 change: 0 additions & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,6 @@ jobs:
release:
name: Open release PR for ${{ inputs.package }}
runs-on: ubuntu-24.04
environment: compact-npm-prod # Requires approval before opening the release PR

permissions:
contents: write # create the release branch
Expand Down
9 changes: 5 additions & 4 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,13 +41,14 @@ release notes agree.
- **Prerelease** - Advance the current beta cycle (`0.4.0-beta.0` ->
`0.4.0-beta.1`). From a stable version it behaves like prepatch.

5. A maintainer must approve the release before it proceeds.
6. Once approved, the CI will automatically:
5. The CI will automatically:
- Run tests.
- Bump the version.
- Open a release PR against the branch you ran from, and auto-merge it.
- Create a git tag.
- Publish the package to npm under the channel's dist-tag.
6. Once the release PR merges, a maintainer must approve the publish. The CI
then:
- Creates a git tag.
- Publishes the package to npm under the channel's dist-tag.
7. Once published, go to "Releases" and create a GitHub release using the
generated tag. Mark beta tags as prereleases.

Expand Down
Loading