Skip to content

fix(dependabot): aim main's config at development - #293

Merged
rubenvdlinde merged 1 commit into
mainfrom
hotfix/dependabot-targets-development
Aug 31, 2026
Merged

fix(dependabot): aim main's config at development#293
rubenvdlinde merged 1 commit into
mainfrom
hotfix/dependabot-targets-development

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

The fleet's default branch is moving to main for every app, and Dependabot reads its config from the DEFAULT branch only. main's copy here predates the target-branch addition, so the moment the default flips, every bump would be opened against main — where branch-protection refuses it and it can never merge.

That is not hypothetical. Measured 2026-08-30, on the ten apps that already defaulted to main:

41 open pull requests across 10 repositories
none mergeable — and Dependabot reopens them as fast as they are closed
App stranded PRs App stranded PRs
zaakafhandelapp 12 dossiq 2
filinq 11 planninq 2
openregister 5 thematiq 1
opencatalogi 3 launchpad 1
integriq 3 stackiq 1

This carries development's canonical config onto main so the flip is safe in either order, rather than depending on the switch and the config landing in the right sequence.

Config only — no code changes.

The default branch is moving to `main` for every app in the fleet, and
Dependabot reads its config from the DEFAULT branch only. Without this,
the flip would send every bump to `main` where branch-protection refuses
it -- the 41-pull-request trap measured across ten other apps on
2026-08-30.

Same content as the development-side change, carried onto main so the
flip is safe in either order.
@rubenvdlinde
rubenvdlinde merged commit 5477698 into main Aug 31, 2026
0 of 10 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.

1 participant