ci(dependabot): target the next branch instead of main#138
Open
ouun wants to merge 1 commit into
Open
Conversation
MilliCache develops on `next` and releases to `main` via release-please, but Dependabot defaulted to the default branch (main). That meant version bumps landed on `main` ahead of the dev branch, and bumps relied on main's workflow — which lagged `next` (e.g. the create-github-app-token client-id migration sat on `next` for weeks while Dependabot PRs against main kept failing the Build Assets check). Point all three ecosystems (composer, npm, github-actions) at `next` so bumps flow through the normal dev branch and run the current workflow. (cherry picked from commit 41b6033)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add
target-branch: "next"to all three Dependabot ecosystems (composer, npm, github-actions) so dependency PRs are opened againstnextinstead of the default branchmain.Why this must live on
mainDependabot reads
.github/dependabot.ymlonly from the default branch (main); thetarget-branchfield then redirects where PRs are raised. So the companion commit onnext(41b6033) has no effect on its own — this PR is what actually activates the behavior.Motivation
MilliCache develops on
nextand releases tomainvia release-please. Dependabot defaulting tomainmeant bumps landed ahead of the dev branch and ran main's (often-lagging) workflow — e.g. thecreate-github-app-tokenclient-idmigration sat onnextfor weeks while Dependabot PRs againstmainkept failing the Build Assets check (#136). Targetingnextkeeps bumps on the branch that's always current.🤖 Generated with Claude Code