slachiewicz opened a new pull request, #161:
URL: https://github.com/apache/maven-scm-publish-plugin/pull/161
`<prerequisites><maven>` reused `${mavenVersion}` — the same property that
sets the `maven-core` / `maven-plugin-api` dependency versions. Bumping those
dependencies therefore raises the plugin's declared Maven baseline as a side
effect, with nothing in the diff saying so.
Pinning the literal `3.6.3` decouples the two: the compile-time dependency
can move, the declared baseline only moves when someone edits it deliberately.
Most of the 3.x plugin line already declares it this way.
No behaviour change — `${mavenVersion}` is `3.6.3` here today. Verified with
`mvn help:evaluate -Dexpression=project.prerequisites.maven`, which returns
`3.6.3` both before and after.
<sub>Drafted with Claude — please verify</sub>
--
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]
