Skip to content

Updating release docs to make it clear that it's ok to merge your own individual package release PRs #3872

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 17, 2025
Merged

Updating release docs to make it clear that it's ok to merge your own individual package release PRs #3872

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5171284
Updating release docs to make it clear that it's ok to merge your own…
aabmass Oct 16, 2025
fd9e8a8
Merge branch 'main' into release-update
aabmass Oct 17, 2025
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: 1 addition & 0 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ to pick a specific package to release. It follows the same versioning strategy a
Long-term package release branch follows `package-release/{package-name}/v{major}.{minor}.x` (or `package-release/{package-name}/v{major}.{minor}bx`) naming pattern.

The workflow will create two pull requests, one against the `main` and one against the `package-release/` branch; both should be merged in order to proceed with the release.
To keep the process lightweight, it's OK to approve the PRs you generate and merge without additional reviews.

## Preparing a new patch release

Expand Down