Bump org.apache.maven.plugins:maven-shade-plugin from 3.6.1 to 3.6.2#224
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin) from 3.6.1 to 3.6.2. - [Release notes](https://github.com/apache/maven-shade-plugin/releases) - [Commits](apache/maven-shade-plugin@maven-shade-plugin-3.6.1...maven-shade-plugin-3.6.2) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-shade-plugin dependency-version: 3.6.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
kaspernielsen
added a commit
that referenced
this pull request
Jul 9, 2026
* Upgrade Maven plugins and test dependencies to latest stable Bump to latest stable releases (verified against repo1.maven.org), superseding the open dependabot PRs and going further where they are stale: - junit-bom 6.0.2 -> 6.1.1 (dependabot #222 targets 6.0.3) - assertj-core 3.26.3 -> 3.27.7 (dependabot #219/#220) - maven-surefire 3.5.4 -> 3.5.6 (dependabot #223 targets 3.5.5) - maven-compiler 3.14.1 -> 3.15.0 (dependabot #221) - maven-resources 3.4.0 -> 3.5.0 (dependabot #225) - maven-shade 3.6.1 -> 3.6.2 (dependabot #224) - maven-enforcer 3.6.2 -> 3.6.3 - maven-invoker 3.9.1 -> 3.10.1 Core 'packed' module builds green: 163 tests pass (0 failures/errors). Pre-existing packed-modulepath-tests compile break is unrelated. * Fix packed-modulepath-tests: repoint Sidehandle* imports to app.packed.extension The Sidehandle* API (SidehandleBinding, SidehandleTargetKind, SidehandleContext) was moved from package app.packed.component to app.packed.extension, but the modulepath test fixtures still imported the old package, breaking compilation of the module. Repointed the 9 stale imports across 5 files; the referenced types, nested Kind enum constants, and installSidebeanIfAbsent signature are otherwise unchanged. Full reactor build is now green (BUILD SUCCESS, all tests pass).
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
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 org.apache.maven.plugins:maven-shade-plugin from 3.6.1 to 3.6.2.
Release notes
Sourced from org.apache.maven.plugins:maven-shade-plugin's releases.
Commits
ad8de59[maven-release-plugin] prepare release maven-shade-plugin-3.6.28eb19dcDrop unneeded dependencies (#788)397b2cdDrop excessive dependencies (#786)eca6398Bug: Extra JARs and Artifacts were not subjected to filtering (#785)7edce17Update to parent POM v 47 (#781)3171a34Mockito improvements (#783)678844bBump org.apache.maven.plugin-testing:maven-plugin-testing-harness (#782)73ec909Bump org.codehaus.mojo:mrm-maven-plugin from 1.7.0 to 1.7.1 (#780)5f7a877Bump org.apache.maven.plugin-testing:maven-plugin-testing-harness (#778)73c5247chore: remove junit3 reference (#762)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)