diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
index 05ea547823..08c63ca77a 100644
--- a/CONTRIBUTORS.md
+++ b/CONTRIBUTORS.md
@@ -56,9 +56,11 @@
 
 ## Maintainers
 
-- Durran Jordan <<durran@gmail.com>>
-- Daria Pardue <<daria.pardue@mongodb.com>>
 - Bailey Pearson <<bailey.pearson@mongodb.com>>
+- Daria Pardue <<daria.pardue@mongodb.com>>
+- Durran Jordan <<durran@gmail.com>>
+- Pavel Safronov <<pavel.safronov@mongodb.com>>
+- Sergey Zelenov <<sergey.zelenov@mongodb.com>>
 
 ## Community Types
 
diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md
index e101231623..464464fcf1 100644
--- a/etc/notes/releasing.md
+++ b/etc/notes/releasing.md
@@ -46,6 +46,9 @@ Merging the release PR will make the action create a Github Release and subseque
 > [!TIP]
 > See the release workflow here: [.github/workflows/release.yml](.github/workflows/release.yml)
 
+> [!TIP]
+> If there have been no releasable units since the last release and you need to force a new release PR to exist (e.g., because you released an alpha and now want to release a major version), you can add the text "Release-As: x.x.x" to any commit body and release-please will open a new PR for that version. Read more [here](https://github.com/googleapis/release-please#how-do-i-change-the-version-number).
+
 ## Release Notes
 
 The contents of the release PR's body becomes the contents of the Github Release.
@@ -153,6 +156,8 @@ an alpha.
 
 Example PR: https://github.com/mongodb-js/mongodb-client-encryption/pull/104
 
+See the tip in the [release-please](#release-please) section for what to do if you need to release a major version with no user-facing changes relative to the last released alpha.
+
 ## Packages
 
 The following is a list of packages the Node.js team is responsible for and these release instructions apply to.