Skip to content

Cap Maven 3 core ignore at 3.11 so 3.10.x patches flow - #647

Open
ascheman wants to merge 1 commit into
apache:masterfrom
aschemaven:bugfix/dependabot-cap-next-minor
Open

ascheman wants to merge 1 commit into
apache:masterfrom
aschemaven:bugfix/dependabot-cap-next-minor

Conversation

@ascheman

@ascheman ascheman commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

This plugin's Maven 3 line (now master) builds against
<mavenVersion>3.10.0</mavenVersion>, but the maven-core /
maven-artifact / maven-plugin-api ignores were capped at >= 3.10.0.
Since the pom is already at 3.10.0, that froze Dependabot at exactly
3.10.0 — even 3.10.x patch releases were ignored.

This raises the cap to >= 3.11.0, matching the pattern on the 3.9-line
plugins (which cap at >= 3.10.0): Dependabot offers patch updates on
the current line, while a Maven-baseline minor bump (3.11) or the jump to
Maven 4 stays a deliberate, human decision. The stale "3.9 baseline"
comment is reworded to describe the 3.10 line this config now governs.

No code or build change — .github/dependabot.yml only.

🤖 Generated with Claude Code

This plugin's Maven 3 line builds against 3.10.0, but the core-artifact
ignores capped at ">= 3.10.0" froze Dependabot at exactly 3.10.0 -- even
3.10.x patches were ignored. Raise the cap to ">= 3.11.0" so patch
updates on the 3.10.x line flow again, while a Maven-baseline minor bump
(3.11) or the jump to Maven 4 stays a deliberate decision. Also reword
the stale "3.9 baseline" comment, which no longer matched this line.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ascheman ascheman added the dependencies Pull requests that update a dependency file label Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant