Skip to content

Commit 5d6f3d9

Browse files
cliffhallclaude
andcommitted
docs(dependabot): state the documented target-branch/security-update rule
Copilot review: the comment read as if `target-branch` had no bearing on security updates. Per GitHub's Dependabot options reference, an entry whose `target-branch` names a non-default branch is not applied to security updates at all — so the schedule/labels/groups here shape version updates only, and security PRs continue to be raised against the default branch. Comment-only; the configured settings are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU
1 parent c8241da commit 5d6f3d9

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

‎.github/dependabot.yml‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,12 @@ version: 2
77
# 1. Dependabot reads it from the DEFAULT branch (`main`). Changes here are
88
# inert until the next milestone merge carries them there.
99
# 2. `target-branch` scopes VERSION updates. Dependabot SECURITY updates are
10-
# enabled in repo settings, not here, and always target the default
10+
# enabled in repo settings, not here, and are raised against the default
1111
# branch — they kept working while this file was missing entirely
12-
# (see #1833, #1840).
12+
# (see #1833, #1840). Per GitHub's Dependabot options reference, an entry
13+
# whose `target-branch` names a non-default branch is NOT applied to
14+
# security updates, so the schedule/labels/groups below shape version
15+
# updates only. Re-confirm security PRs still appear after this lands.
1316
#
1417
# v2 is not an npm workspace: the root and each client under `clients/*` carry
1518
# their own package.json + lockfile, so each needs its own entry.

0 commit comments

Comments
 (0)