Skip to content

docs: clarify release notes verification steps #4960

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
dariakp merged 3 commits into from
Jun 12, 2026
+5 −3
Merged

docs: clarify release notes verification steps #4960

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7599bd4
docs: clarify release notes verification steps
dariakp Jun 9, 2026
a9cd3e5
Additional clarifications
dariakp Jun 9, 2026
4048165
Potential fix for pull request finding
PavelSafronov Jun 12, 2026
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
8 changes: 5 additions & 3 deletions etc/notes/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,9 +78,11 @@ The MongoDB driver can now generate a cup of joe.
- You may skip this step if you are releasing a package other than the driver.
1. Comment "`run release_notes`" on the release PR.
- This will kick off the action that reads the notes from each PR going into the release.
- Double check the result looks logically organized
- You may edit the PR body for any quick edits or re-orderings.
- If there are a number of changes, edit the original PRs and post a new `run` comment
- Double check the result looks logically organized and complete
- As a rule of thumb, every `feat` and `fix` should have a corresponding release note
- Cross-reference the list of tickets in the corresponding JIRA release for consistency
- You may modify the release PR body directly for any quick edits or re-orderings.
- If there are any non-cosmetic changes, edit the original PRs and post a new `run release_notes` comment
1. Merge the release PR
- If this is a release to a previous major, navigate to the new release and reset "latest" to our latest release in our _current_ major.
1. If this is a new driver minor release, generate the new documentation
Expand Down
Loading