build(deps): bump plugin from 4.16 to 4.50

Created by: dependabot[bot]

Bumps plugin from 4.16 to 4.50.

Release notes

Sourced from plugin's releases.

4.50

💥 Breaking changes

• Remove --mutex network argument for Yarn builds (#625) @​scherler

If you previously relied on the --mutex network argument (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.

• Remove direct dependency on JCIP annotations (#633) @​basil

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

• Support multi-module Maven projects when using a SpotBugs exclude filter file (#631) @​basil

📦 Dependency updates

• Upgrade spotbugs-maven-plugin from 4.2.3 to 4.7.3.0 (#639, #638, #637, #629) @​basil @​dependabot
• Upgrade maven-release-plugin from 3.0.0-M6 to 3.0.0-M7 (#630) @​dependabot

4.49

💥 Breaking changes

• Remove <node.version>, <npm.version>, and <yarn.version> defaults (#614, #626) @​NotMyFault

If 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).

Check the build log for the following parts: you-must-override-the-yarn.version-property, you-must-override-the-node.version-property and you-must-override-the-npm.version-property. If one or more are present, they specify the tool you need to add a version for. You can obtain available versions here:

• Node: https://nodejs.org/ - We recommend to use LTS versions
• NPM: https://www.npmjs.com/package/npm?activeTab=versions
• Yarn: https://github.com/yarnpkg/berry/releases

📦 Dependency updates

• Bump maven-license-plugin from 1.10 to 1.15 (#624, #622) @​dependabot
• Bump jenkins-test-harness from 1847.v10c7a_4c2e344 to 1868.v03b_7c6673e2e (#623, #619, #617, #615) @​dependabot
• Bump gmavenplus-plugin from 1.13.1 to 2.1.0 (#621, #618) @​dependabot
• Bump mockito-bom from 4.8.0 to 4.8.1 (#620) @​dependabot
• Bump maven-hpi-plugin from 3.34 to 3.35 (#616) @​dependabot

4.48

📦 Dependency updates

• Bump JUnit from 5.9.0 to 5.9.1 (#613) @​dependabot

... (truncated)

Commits

• 75821e1 [maven-release-plugin] prepare release plugin-4.50
• 95f86ce Bump spotbugs-maven-plugin from 4.7.2.2 to 4.7.3.0 (#639)
• 0140be6 Remove --mutex network argument for Yarn builds (#625)
• 2d5d344 Bump spotbugs-maven-plugin from 4.7.2.1 to 4.7.2.2 (#637)
• 161a27f Bump spotbugs-maven-plugin from 4.7.2.1 to 4.7.2.2 (#638)
• 61707aa Sort \<dependencyManagement> section by scope, group ID, and artifact ID (#636)
• dd938c8 Sort \<pluginManagement> entries by group ID and artifact ID (#635)
• 1467932 Remove managed dependency on Objenesis (#634)
• d76e635 Remove explicit dependency on jcip-annotations (#633)
• 994fd6b Sort \<dependencyManagement> section by group ID and artifact ID (#632)
• 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 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 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)