Update advanced-security/maven-dependency-submission-action action to v5#136
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the following updates:
v4→v5Release Notes
advanced-security/maven-dependency-submission-action (advanced-security/maven-dependency-submission-action)
v5Compare Source
v5.0.0Compare Source
Improved multi-module support
This release improves multi-module support by reflecting which
pom.xmlfile brings in a particular dependency. Previously, the dependencies were aggregated into the top-levelpom.xmlfile. If a given package is brought in via multiple modules, that package will be reflected in all of the modules that reference it.Because of this change in behavior, we've removed two configuration options:
snapshot-dependency-file-name: no longer applicable since we submit more than one manifestsnapshot-include-file-name: this flag determined whether the manifest object included the file path. It should always be available and there's no reason to omit it, so we've removed the flag.v4.1.3Compare Source
The release bumps dependency versions to stay up-to-date.
v4.1.2Compare Source
What's Changed
New Contributors
Full Changelog: advanced-security/maven-dependency-submission-action@v4...v4.1.2
v4.1.1Compare Source
v4.1.0Compare Source
Adds the ability to change the detector details for the dependency snapshots via the optional input parameters:
detector-namedetector-urldetector-versionIf the
detector-nameis specified, then all three become mandatory as there are no sensible defaults that can be attributed to the values.v4.1Compare Source
v4.0.3Compare Source
Updating the build process and tooling for Node 20 support in the CLI executables which were introduced when the dependency-submission-toolkit transitioned in to an ESM module
Fixes #69 #61
v4.0.2Compare Source
v4.0.1Compare Source
dependency-submission-toolkitbroke the4.0.0pkgbased executable builds.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.