From 7599bd401a3362df76281828a7a06912b36bb0c7 Mon Sep 17 00:00:00 2001 From: Daria Pardue Date: Tue, 9 Jun 2026 14:22:50 -0400 Subject: [PATCH 1/3] docs: clarify release notes verification steps Clarify instructions for checking release notes completeness and organization. --- etc/notes/releasing.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md index f74509eec3..cabdbf85a8 100644 --- a/etc/notes/releasing.md +++ b/etc/notes/releasing.md @@ -78,7 +78,9 @@ 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 + - 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 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 1. Merge the release PR From a9cd3e5da4b598bb880d78c71096368cb0254e2b Mon Sep 17 00:00:00 2001 From: Daria Pardue Date: Tue, 9 Jun 2026 14:39:15 -0400 Subject: [PATCH 2/3] Additional clarifications Co-authored-by: Daria Pardue --- etc/notes/releasing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md index cabdbf85a8..0ab8666b29 100644 --- a/etc/notes/releasing.md +++ b/etc/notes/releasing.md @@ -81,8 +81,8 @@ The MongoDB driver can now generate a cup of joe. - 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 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 + - 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 From 40481658de4235b5d7a6b55d8b3f0c57b13a2e7d Mon Sep 17 00:00:00 2001 From: Pavel Safronov Date: Fri, 12 Jun 2026 07:52:28 -0700 Subject: [PATCH 3/3] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- etc/notes/releasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md index 0ab8666b29..4d001460b8 100644 --- a/etc/notes/releasing.md +++ b/etc/notes/releasing.md @@ -80,7 +80,7 @@ The MongoDB driver can now generate a cup of joe. - This will kick off the action that reads the notes from each PR going into the release. - 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 + - 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