Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies the documented backport/release-branch setup process by splitting the instructions into an ordered sequence and emphasizing that the release action backport should be the first PR on a release branch.
Changes:
- Reworded and restructured the “Backports” section to make the sequence of steps clearer.
- Added explicit guidance to open/merge the release action PR before expecting release-please automation to work on the release branch.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
etc/notes/releasing.md
Outdated
| Now, the release-please will work the same as `main`. Any PRs that merge to the release branch trigger the release action and update release-pleases' release PR. Proceed as normal from here. | ||
| First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Double check that there isn't any release tooling on main that doesn't exist on the target branch. If there is, make sure this is backported too. Check if the target branch has a release-please config and manifest file. If not, make sure to adopt changes for release-please v4 (see https://github.com/mongodb/js-bson/pull/682 as an example). Backport all of the above changes to the target release branch and open a PR. | ||
|
|
||
| Once the release action PR is merged, release-please will work on this branch in the same was as it does on `main`. Any PRs that merge to the release branch trigger the release action and update release-pleases' release PR. Proceed as normal from here. |
dariakp
reviewed
Mar 18, 2026
Co-authored-by: Daria Pardue <daria.pardue@mongodb.com>
Co-authored-by: Daria Pardue <daria.pardue@mongodb.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release/backport documentation to make the “backport the release action” step clearer and explicitly position it as the first PR on a new release branch.
Changes:
- Rewords the backport instructions to split them into clearer steps.
- Adds guidance to verify CI after opening the release-action backport PR.
- Clarifies expected release-please behavior after the release-action PR merges.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
dariakp
added
the
Primary Review
dariakp
requested changes
Mar 18, 2026
Co-authored-by: Daria Pardue <daria.pardue@mongodb.com>
dariakp
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Summary of Changes
Notes for Reviewers
What is the motivation for this change?
Release Highlight
Release notes highlight
Double check the following
npm run check:lint)type(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript