From f026e53c976d54555f660fc250ca17cf523532ef Mon Sep 17 00:00:00 2001
From: Daria Pardue <daria.pardue@mongodb.com>
Date: Sun, 22 Mar 2026 13:10:42 -0400
Subject: [PATCH 1/2] chore: update codeql target for v7.1.x

---
 .github/workflows/codeql.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
index fe360b18b69..dc12be9765b 100644
--- a/.github/workflows/codeql.yml
+++ b/.github/workflows/codeql.yml
@@ -2,9 +2,9 @@ name: "CodeQL"
 
 on:
   push:
-    branches: [ "main", "5.x" ]
+    branches: [ "main", "v7.1.x" ]
   pull_request:
-    branches: [ "main", "5.x" ]
+    branches: [ "main", "v7.1.x" ]
 
 jobs:
   analyze:

From b2893f3793c2c3bf705ac623cbfb3998a85a8f71 Mon Sep 17 00:00:00 2001
From: Daria Pardue <daria.pardue@mongodb.com>
Date: Sun, 22 Mar 2026 13:55:23 -0400
Subject: [PATCH 2/2] docs: update release instructions with codeql

---
 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 fe5703c9a5d..0a6df4c4f0f 100644
--- a/etc/notes/releasing.md
+++ b/etc/notes/releasing.md
@@ -32,7 +32,7 @@ release-please automatically tags release commits with a tag in the format v<maj
 
 Then, backport the release action to the target release branch. This should be done as the first PR on the release branch. Use the following instructions to create it.
 
-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. After opening the PR, check the CI to make sure everything works as expected: add backports of CI fixes as needed.
+First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Also, add the branch to the list of CodeQL target branches (codeql.yml). 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. After opening the PR, check the CI to make sure everything works as expected: add backports of CI fixes as needed.
 
 Once the release action PR is merged, release-please will work on this branch in the same way as it does on `main`. Any PRs that merge to the release branch trigger the release action and update the release PR that release-please manages. Proceed as normal from here.