build(deps): bump plugin from 4.16 to 4.51
Created by: dependabot[bot]
Bumps plugin from 4.16 to 4.51.
Release notes
Sourced from plugin's releases.
4.51
🚀 New features and improvements
🐛 Bug fixes
📝 Documentation updates
- Document Java 17 support (#643)
@NotMyFault
📦 Dependency updates
- Bump Maven Install Plugin from 3.0.1 to 3.1.0 (#646)
@dependabot- Bump
jenkins-test-harnessfrom 1868.v03b_7c6673e2e to 1894.v471a_047124ce (#647, #644, #641)@dependabot- Bump Mockito from 4.8.1 to 4.9.0 (#642)
@dependabot4.50
💥 Breaking changes
- Remove
--mutex networkargument for Yarn builds (#625)@scherlerIf you previously relied on the
--mutex networkargument (for example, to ensure that only one instance of Yarn runs at any given time when running multiple instances of Yarn as the same user on the same server when running Yarn 1.x), you must now opt in to this behavior explicitly by adding<frontend.yarn.arguments>--mutex network</frontend.yarn.arguments>to the<properties>section of your plugin POM.The direct dependency on JCIP annotations has been removed from the plugin POM. Plugins that use JCIP annotations should ensure they have a core baseline of 2.326 or later.
🚨 Removed
- Remove managed dependency on Objenesis (#634)
@basil- Remove duplicate SpotBugs defaults (#628)
@basil
🐛 Bug fixes
📦 Dependency updates
- Upgrade
spotbugs-maven-pluginfrom 4.2.3 to 4.7.3.0 (#639, #638, #637, #629)@basil@dependabot- Upgrade
maven-release-pluginfrom 3.0.0-M6 to 3.0.0-M7 (#630)@dependabot4.49
💥 Breaking changes
- Remove
<node.version>,<npm.version>, and<yarn.version>defaults (#614, #626)@NotMyFaultIf you previously used this functionality but did not explicitly specify a Node, NPM, or Yarn version, you must now explicitly specify the version in your
pom.xml(or gradle build scripts).
... (truncated)
Commits
-
e8ea72a[maven-release-plugin] prepare release plugin-4.51 -
fe4cf3fBumpmaven-install-pluginfrom 3.0.1 to 3.1.0 (#646) -
524d3c8Bumpjenkins-test-harnessfrom 1881.v5d4b_a_f650249 to 1894.v471a_047124ce ... -
7ebe9afUseproject.basedirrather thanmaven.multiModuleProjectDirectory(#648) -
0e51782Merge pull request #645 from jglick/surefire.forkNumber -
157e25aDefinesurefire.forkNumberin Surefire JVM -
e2e855bBumpjenkins-test-harnessfrom 1875.vf39637878e43 to 1881.v5d4b_a_f650249 (... -
39349f2Document Java 17 support (#643) -
9ba9112Bump mockito-bom from 4.8.1 to 4.9.0 (#642) -
71f6b77Bump jenkins-test-harness from 1868.v03b_7c6673e2e to 1875.vf39637878e43 (#641) - Additional commits viewable in compare view
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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)