This is an automated email from the ASF dual-hosted git repository. ascheman pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/maven-clean-plugin.git
commit b8c3f44599e9ddeeadd066af11fd5d5499fe7315 Author: Gerd Aschemann <[email protected]> AuthorDate: Tue Nov 3 18:27:16 2026 +0100 Cap core ignore at next minor (3.11) not 4.0.0 Unify with the 3.9-line plugins' pattern: cap the core-artifact ignores at the next minor rather than at Maven 4. On this 3.10.0 line that means ">= 3.11.0" -- Dependabot still offers 3.10.x patches, while the 3.11 minor bump (or the jump to Maven 4) stays a deliberate decision. Co-Authored-By: Claude Opus 4.8 <[email protected]> --- .github/dependabot.yml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 33bf9f1..d58bde1 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -45,13 +45,16 @@ updates: - dependency-name: "org.apache.maven.resolver:*" versions: [">= 2.0.0"] # This plugin's Maven 3 line builds against 3.10.0 (see <mavenVersion>), so - # keep it on the 3.10.x line and only block the jump to Maven 4. Scoped to - # the core artifacts this plugin uses; other org.apache.maven:* artifacts - # with their own release line are untouched. + # keep it on the 3.10.x line. Cap the core-artifact ignores at the next + # minor (3.11) so Dependabot still offers 3.10.x patches, while a + # Maven-baseline minor bump (3.11) or the jump to Maven 4 stays a + # deliberate decision. Scoped to the core artifacts this plugin uses; + # other org.apache.maven:* artifacts with their own release line are + # untouched. - dependency-name: "org.apache.maven:maven-core" - versions: [">= 4.0.0"] + versions: [">= 3.11.0"] - dependency-name: "org.apache.maven:maven-plugin-api" - versions: [">= 4.0.0"] + versions: [">= 3.11.0"] - package-ecosystem: "github-actions" directory: "/"
