Skip to content

docs(dependabot): clarify security-update routing to main (#1341)#1346

Merged
vybe merged 1 commit into
devfrom
fix/1341-dependabot-security-routing-note
Jun 26, 2026
Merged

docs(dependabot): clarify security-update routing to main (#1341)#1346
vybe merged 1 commit into
devfrom
fix/1341-dependabot-security-routing-note

Conversation

@dolho

@dolho dolho commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Related to #1341

Comment-only clarification in .github/dependabot.yml. No behavioral change.

Context

Investigating #1341 showed the config bug it describes was already fixed: target-branch: dev is set on all 6 ecosystem entries on both main and dev (live on main since v0.6.1, 2026-06-12). Version-update PRs correctly target dev.

The two PRs still on main (#1298 form-data, #1324 vite 5→8) are Dependabot security updates — created after the config was live, branch names lack the /dev/ segment, and #1324 is a major bump the patch-and-minor group would never raise. GitHub routes security updates to the default branch (main) by design; target-branch can't redirect them, and closing them triggers a recreate loop.

Change

Expands the header comment to spell out that a security PR against main is expected, not a misroute, and what to do (let it merge to main as a security fix → reaches dev on the next back-merge, or cherry-pick if urgent). Prevents this from being re-filed as a config bug.

🤖 Generated with Claude Code

…1341)

The config already sets `target-branch: dev` on every ecosystem (live on main
since v0.6.1), so version-update PRs correctly flow to dev. The remaining
symptom in #1341 — Dependabot *security* PRs (#1298 form-data, #1324 vite)
opening against `main` — is GitHub's by-design routing: security updates ignore
`target-branch` and always target the default branch, and closing them triggers
a recreate loop. Spell that out in the config comment with what to do instead
(merge to main as a security fix; reaches dev on the next back-merge, or
cherry-pick if urgent), so this isn't re-filed as a config bug.

No behavioral change — comment only.

Related to #1341

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

⚠️ Nightly unit-suite check skipped — merge conflict against dev.

Resolve by running git merge dev locally and pushing the result. The next nightly run will re-test once the conflict is gone.

@vybe vybe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validated via /validate-pr: docs/config only, security clean. Approving.

@vybe vybe merged commit 943d78e into dev Jun 26, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants