Repository navigation
2.25.0
Versions Maven Plugin 2.25.0 stops suggesting pre-release versions by default, can hold back releases until they have been published for a set number of days, and can follow the ignore rules of a project's Dependabot configuration. It requires Maven 3.9.0 or later and Java 8 or later.
✨ Highlights
- Pre-releases are left out by default: every goal and report now skips alpha, beta, milestone, release-candidate, preview and early-access versions, so the newest stable version is reported instead of, say,
3.34.0.CR1. Pass-DallowPreReleases=trueto get the previous output. When the current version is itself a pre-release or snapshot, newer pre-releases of the same release line are still offered: from4.0.0-beta-3, both4.0.0-beta-4and4.0.0are offered (#1482). minimumReleaseAge: offer a release as an update only after it has been published for the given number of days (-Dversions.minimumReleaseAge=7).minimumReleaseAgeExcludesexempts trustedgroupId:artifactIdpatterns. The publication date is read through Maven's own transport, so proxies, mirrors and server credentials apply (#1484).- Dependabot ignore rules: with
-Dversions.dependabotConfig=.github/dependabot.yml, the goals and reports skip the versions that the Dependabot configuration ignores for the branch being built (#1480). processPluginsfor theuse-latest-*anduse-next-*goals: these goals can now also update plugins with a literal version inbuild/plugins,build/pluginManagementandreporting. A plugin version that needs a newer Maven than the project's minimum is skipped (#1477).set-property -Dinsert: adds a property the POM doesn't declare yet, optionally inside a profile given withprofileId(#1340).rulesUriis loaded through the Maven Resolver: it works with whichever transports Maven is configured with, and the Wagon dependencies are gone. Code that constructs the mojos, reports or themaxDependencyUpdatesenforcer rule directly now passes aTransporterProviderinstead of aMap<String, Wagon>(#1475).- Fixes: BOMs imported as
${project.groupId}:bom:${project.version}no longer fail with "Not fully interpolated artifact" on Maven 3.10 and 4 (#1486). A property that only a child module uses is evaluated with that module's rules again, as in 2.22.0 (#1481).numThreadsis honored by theuse-latest-*anduse-next-*goals (#1478).
🚨 Removed
- Leave pre-release versions out by default in every goal and report (#1482) @slachiewicz
🚀 New features and improvements
- Add minimumReleaseAge to hold back recent releases (#1484) @slachiewicz, carrying a commit by @Master-Code-Programmer
- Apply the ignore rules from the Dependabot configuration (#1480) @slachiewicz
- set-property should add the property if it does not yet exist (#1340) @mandritschke
- Load rulesUri through the Resolver transporter instead of Wagon (#1475) @slachiewicz
- Update plugin versions with processPlugins in the use-latest and use-next goals (#1477) @slachiewicz
🐛 Bug Fixes
- Interpolate raw dependencyManagement coordinates before resolving versions (#1486) @slachiewicz
- Allow downgrading x.0.0-SNAPSHOT to an x.0.0 pre-release with allowMajorUpdates=false (#1374) @dcolazin
- Evaluate a parent property used only by a module in that module (#1481) @slachiewicz
- Honor numThreads in the use-latest and use-next goals (#1478) @slachiewicz
📦 Dependency updates
- Remove the maven-shared-utils dependency (#1483) @slachiewicz
- Use doxiaVersion for doxia-module-xhtml5 (#1476) @slachiewicz
Thanks to @dcolazin, @mandritschke, @Master-Code-Programmer and @slachiewicz.