slachiewicz commented on PR #279: URL: https://github.com/apache/maven-plugin-testing/pull/279#issuecomment-5233655472
Closing this — I had the diagnosis backwards. I read `target-branch: maven-plugin-testing-3.x` on both entries as a misconfiguration that left `master` uncovered. It is not: this component has been merged into the Maven core repository, and `master` here is a tombstone. The README says so directly: > Maven Plugin Testing has been merged into Maven core repository. > Branches are still available: > * maven-plugin-testing-3.x for Maven 3.x So pointing Dependabot at `maven-plugin-testing-3.x` only is exactly right — it is the one branch still alive. Adding default-branch entries would have generated update PRs against a branch nobody develops on. That also explains what I took as evidence of the bug: the 3.x branch being on `@v5` while `master` sits on `@v4` is not the maintenance line running ahead of the default branch, it is the live branch being maintained and the dead one being left alone. `master` staying on `@v4` is not a problem to fix. Apologies for the noise. -- 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]
