From 12471a92ba6e23780eab6c11cad8fb2fa8ca75f6 Mon Sep 17 00:00:00 2001 From: Pavel Safronov Date: Thu, 12 Nov 2026 09:38:06 -0800 Subject: [PATCH 1/2] docs: update release docs to reference new slack workflow --- etc/notes/releasing.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md index 02752629f6..f98098d560 100644 --- a/etc/notes/releasing.md +++ b/etc/notes/releasing.md @@ -13,7 +13,7 @@ - [Packages](#packages) > [!NOTE] -> _Last updated: Oct 1, 2025_ +> _Last updated: Nov 12, 2026_ ## Pre-requisites @@ -78,7 +78,9 @@ The MongoDB driver can now generate a cup of joe. - Check the JIRA release to make sure all work tagged for this release has been completed. - Check CI for failures. - Check the performance metrics to make sure there are no regressions. -1. On slack notify `#node-driver-docs`, `#nodejs-devtools`, and `#mongoose` that we intend to publish a release. +1. Announce the upcoming release on Slack by running the **Node Driver pre-release announcements** workflow. + - Find it in the `#nodejs-team` channel, under the **Workflows** tab. + - The workflow posts the announcement to every channel that should hear about an upcoming driver release, so you do not need to post to those channels yourself. - You may skip this step if you are releasing a package other than the driver. 1. **If there are new or changed experimental features**, update `EXPERIMENTAL_FEATURES.md` - Add descriptions for any new `@experimental` features From 0a86973c7df8d11c0317c00943a49d2821240ca2 Mon Sep 17 00:00:00 2001 From: Pavel Safronov Date: Fri, 13 Nov 2026 08:42:25 -0800 Subject: [PATCH 2/2] pr feedback --- 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 f98098d560..c0956a82ab 100644 --- a/etc/notes/releasing.md +++ b/etc/notes/releasing.md @@ -79,7 +79,7 @@ The MongoDB driver can now generate a cup of joe. - Check CI for failures. - Check the performance metrics to make sure there are no regressions. 1. Announce the upcoming release on Slack by running the **Node Driver pre-release announcements** workflow. - - Find it in the `#nodejs-team` channel, under the **Workflows** tab. + - Find it in the team slack channel, under the **Workflows** tab. - The workflow posts the announcement to every channel that should hear about an upcoming driver release, so you do not need to post to those channels yourself. - You may skip this step if you are releasing a package other than the driver. 1. **If there are new or changed experimental features**, update `EXPERIMENTAL_FEATURES.md`