slachiewicz opened a new pull request, #279:
URL: https://github.com/apache/maven-plugin-testing/pull/279
Both entries in `dependabot.yml` carry `target-branch:
"maven-plugin-testing-3.x"`. That setting **replaces** the default target
rather than adding to it, so Dependabot has only ever proposed updates for the
maintenance branch — nothing has been proposed for `master` since it was added.
The effect is visible in the workflows, and it is the wrong way round:
```
maven-plugin-testing-3.x pr-automation.yml @v5
release-drafter.yml @v5
maven-verify.yml @v5
master pr-automation.yml @v4
release-drafter.yml @v4
```
The maintenance branch is ahead of the default branch, because its bump PRs
(#276, #277, #278) landed there and `master` never got any.
This adds the same two ecosystems again without `target-branch`, so `master`
is covered. The existing 3.x entries are untouched — purely additive, four
entries instead of two.
Found while working through apache/maven-gh-actions-shared#247, which tracks
moving the org off the `v4` shared workflows. This repository is the only one
in the org with this inversion; the other 84 with a `github-actions` ecosystem
all cover their default branch.
Once this merges Dependabot should propose the `@v4` → `@v5` bumps for
`master` on its next run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
