mojohaus / buildnumber-maven-plugin

BuildNumber Maven Plugin
https://www.mojohaus.org/buildnumber-maven-plugin/
MIT License
66 stars 57 forks source link

Bump org.apache.maven:apache-maven from 3.6.3 to 3.9.6 #218

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps org.apache.maven:apache-maven from 3.6.3 to 3.9.6.

Release notes

Sourced from org.apache.maven:apache-maven's releases.

3.9.6

Release Notes - Maven - Version 3.9.6

Improvement

  • [MNG-7939] - Allow to exclude plugins from validation

Dependency upgrade

  • [MNG-7913] - Upgrade Sisu version to 0.9.0.M2
  • [MNG-7934] - Upgrade Resolver version to 1.9.18
  • [MNG-7942] - Upgrade to parent POM 41
  • [MNG-7943] - Upgrade default plugin bindings

3.9.5

Release Notes - Maven - Version 3.9.5

Bug

  • [MNG-7851] - Error message when modelVersion is 4.0 is confusing

Improvement

  • [MNG-7875] - colorize transfer messages
  • [MNG-7895] - Support ${project.basedir} in file profile activation

Task

  • [MNG-7856] - Maven Resolver Provider classes ctor change
  • [MNG-7870] - Undeprecate wrongly deprecated repository metadata
  • [MNG-7872] - Deprecate org.apache.maven.repository.internal.MavenResolverModule
  • [MNG-7874] - maven-resolver-provider: introduce NAME constants.

Dependency upgrade

  • [MNG-7859] - Update to Resolver 1.9.16

3.9.4

Release Notes - Maven - Version 3.9.4

... (truncated)

Commits
  • bc0240f [maven-release-plugin] prepare release maven-3.9.6
  • e6cc6c5 [MNG-7943] Upgrade default plugin bindings
  • 48adee3 [MNG-7934] Update to Resolver 1.9.18 (#1326)
  • da6c7e4 [MNG-7942] Upgrade maven-parent to 41
  • 95fa548 [MNG-7934] Update to Resolver 1.9.17 (#1321)
  • c54baa6 [MNG-7939] Allow to exclude plugins from validation
  • ecd59b7 [MNG-7913] Upgrade Sisu version (#1286)
  • 53edd71 Use the same branch name for ITs on Jenkins (#1263)
  • 2bc4449 The maven-3.9.x branch should fallback to maven-3.9.x branch of ITs
  • 6e532cd [maven-release-plugin] prepare for next development iteration
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 7 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.