Bump the maven group across 1 directory with 6 updates #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps the maven group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | org.apache.maven:maven-core | `3.9.6` | `3.9.9` | | [org.apache.maven.plugins:maven-surefire-plugin](https://github.com/apache/maven-surefire) | `3.2.5` | `3.5.2` | | [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin) | `3.5.2` | `3.6.0` | | [org.apache.maven.plugins:maven-release-plugin](https://github.com/apache/maven-release) | `3.0.1` | `3.1.1` | | org.sonatype.plugins:nexus-staging-maven-plugin | `1.6.13` | `1.7.0` | | [org.apache.maven.plugins:maven-javadoc-plugin](https://github.com/apache/maven-javadoc-plugin) | `3.6.3` | `3.11.1` | Updates `org.apache.maven:maven-core` from 3.9.6 to 3.9.9 Updates `org.apache.maven.plugins:maven-surefire-plugin` from 3.2.5 to 3.5.2 - [Release notes](https://github.com/apache/maven-surefire/releases) - [Commits](apache/maven-surefire@surefire-3.2.5...surefire-3.5.2) Updates `org.apache.maven.plugins:maven-shade-plugin` from 3.5.2 to 3.6.0 - [Release notes](https://github.com/apache/maven-shade-plugin/releases) - [Commits](apache/maven-shade-plugin@maven-shade-plugin-3.5.2...maven-shade-plugin-3.6.0) Updates `org.apache.maven.plugins:maven-release-plugin` from 3.0.1 to 3.1.1 - [Release notes](https://github.com/apache/maven-release/releases) - [Commits](apache/maven-release@maven-release-3.0.1...maven-release-3.1.1) Updates `org.sonatype.plugins:nexus-staging-maven-plugin` from 1.6.13 to 1.7.0 Updates `org.apache.maven.plugins:maven-javadoc-plugin` from 3.6.3 to 3.11.1 - [Release notes](https://github.com/apache/maven-javadoc-plugin/releases) - [Commits](apache/maven-javadoc-plugin@maven-javadoc-plugin-3.6.3...maven-javadoc-plugin-3.11.1) --- updated-dependencies: - dependency-name: org.apache.maven:maven-core dependency-type: direct:production update-type: version-update:semver-patch dependency-group: maven - dependency-name: org.apache.maven.plugins:maven-surefire-plugin dependency-type: direct:production update-type: version-update:semver-minor dependency-group: maven - dependency-name: org.apache.maven.plugins:maven-shade-plugin dependency-type: direct:production update-type: version-update:semver-minor dependency-group: maven - dependency-name: org.apache.maven.plugins:maven-release-plugin dependency-type: direct:production update-type: version-update:semver-minor dependency-group: maven - dependency-name: org.sonatype.plugins:nexus-staging-maven-plugin dependency-type: direct:production update-type: version-update:semver-minor dependency-group: maven - dependency-name: org.apache.maven.plugins:maven-javadoc-plugin dependency-type: direct:production update-type: version-update:semver-minor dependency-group: maven ... Signed-off-by: dependabot[bot] <[email protected]>
marko-bekhta
force-pushed
the
dependabot/maven/maven-cac8843998
branch
from
3dd7eb1 to
13589fc
Compare
marko-bekhta
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the maven group with 6 updates in the / directory:
3.9.63.9.93.2.53.5.23.5.23.6.03.0.13.1.11.6.131.7.03.6.33.11.1Updates
org.apache.maven:maven-corefrom 3.9.6 to 3.9.9Updates
org.apache.maven.plugins:maven-surefire-pluginfrom 3.2.5 to 3.5.2Release notes
Sourced from org.apache.maven.plugins:maven-surefire-plugin's releases.
... (truncated)
Commits
ea9f049[maven-release-plugin] prepare release surefire-3.5.2e1f94a0[SUREFIRE-2276] JUnit5's TestTemplate failures treated as flakes with retriesd24adb4[SUREFIRE-2277] RunResult#getFlakes() is lost during serialisation/deserialis...4385e94Remove links to non-existing report8881971Remove outdated FAQ0121834[SUREFIRE-2283] FAQ site contains broken link to failsafe-plugin91d16c3Fix formatting of XML schema files6cb417aAdd .xsd to .gitattributes9ce5221[SUREFIRE-2282] surefire-report-plugin: Update Introduction documentation page620b983[SUREFIRE-2281] Upgrade to Doxia 2.0.0 GA StackUpdates
org.apache.maven.plugins:maven-shade-pluginfrom 3.5.2 to 3.6.0Commits
9a572e2[maven-release-plugin] prepare release maven-shade-plugin-3.6.0ade2e35[MSHADE-428] Prevent null value in array of transformers (#229)b573b8c[MSHADE-478] Extra JARs feature (#228)199ffaeDrop the cruft (#225)912a81dBump maven-gh-actions-shared to v480e4420[maven-release-plugin] prepare for next development iteration19618cd[maven-release-plugin] prepare release maven-shade-plugin-3.5.3faf233e[MSHADE-472] upgrade parent POM7de9ae7[MSHADE-471] deal with DST58d8cfe[MSHADE-470] Bump asmVersion from 9.6 to 9.7 (#218)Updates
org.apache.maven.plugins:maven-release-pluginfrom 3.0.1 to 3.1.1Release notes
Sourced from org.apache.maven.plugins:maven-release-plugin's releases.
Commits
4f350d4[maven-release-plugin] prepare release maven-release-3.1.106f6de4[MRELEASE-1153] Revert parts of MRELEASE-1109 (8dfcb47996320af5e6f0b2d50eac20...985d0bc[MRELEASE-1149] Current release of the plugin has configuration docs missing47e94b4[maven-release-plugin] prepare for next development iterationf2f9f4e[maven-release-plugin] prepare release maven-release-3.1.0e109d3bBump scmVersion from 2.0.1 to 2.1.05f794a1Bump org.apache.maven.shared:maven-invoker from 3.2.0 to 3.3.028201bbBump org.codehaus.plexus:plexus-interactivity-api from 1.2 to 1.38547606Bump org.codehaus.plexus:plexus-interpolation from 1.26 to 1.27adf6aafBump org.xmlunit:xmlunit-core from 2.9.1 to 2.10.0Updates
org.sonatype.plugins:nexus-staging-maven-pluginfrom 1.6.13 to 1.7.0Updates
org.apache.maven.plugins:maven-javadoc-pluginfrom 3.6.3 to 3.11.1Release notes
Sourced from org.apache.maven.plugins:maven-javadoc-plugin's releases.
... (truncated)
Commits
619650c[maven-release-plugin] prepare release maven-javadoc-plugin-3.11.1e314da0[MJAVADOC-821] Align toolchain discovery code with Maven Compiler Plugin62a6861[MJAVADOC-820] [REGRESSION] MJAVADOC-787 was merged incompletelyd1090c5[maven-release-plugin] prepare for next development iterationee030f7[maven-release-plugin] prepare release maven-javadoc-plugin-3.11.06c5fdc0[MJAVADOC-819] Align archive generation code with Maven Source Plugin3a90de5[MJAVADOC-787] Automatic detection of release option for JDK < 9373172d[MJAVADOC-817] Upgrade to Doxia 2.0.0 GA Stackba266c0Fix SCM tag5775ce1Fix typoDependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions