Bump advanced-security/maven-dependency-submission-action from 4 to 5

[dependabot]

Bumps advanced-security/maven-dependency-submission-action from 4 to 5.

Release notes

Sourced from advanced-security/maven-dependency-submission-action's releases.

v5.0.0

Improved multi-module support

This release improves multi-module support by reflecting which pom.xml file brings in a particular dependency. Previously, the dependencies were aggregated into the top-level pom.xml file. 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 manifest
• snapshot-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.3

The release bumps dependency versions to stay up-to-date.

v4.1.2

What's Changed

• Add cycle safety for transitive dependencies by @​juxtin in advanced-security/maven-dependency-submission-action#103

New Contributors

• @​juxtin made their first contribution in advanced-security/maven-dependency-submission-action#103

Full Changelog: advanced-security/maven-dependency-submission-action@v4...v4.1.2

v4.1.1

No release notes provided.

v4.1.0

• Adds the ability to change the detector details for the dependency snapshots via the optional input parameters:

  • detector-name
  • detector-url
  • detector-version

  If the detector-name is specified, then all three become mandatory as there are no sensible defaults that can be attributed to the values.

v4.0.3

• 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.2

No release notes provided.

v4.0.1

• Updating branding for the marketplace
• Utilizing rollup to build cli executables as the ESM module for the dependency-submission-toolkit broke the 4.0.0 pkg based executable builds.

Commits

• b275d12 Merge pull request #114 from advanced-security/contrib-5.0
• bdc082b Bump the tag mentioned in the contrib doc to v5
• 2c65a53 Merge pull request #110 from advanced-security/juxtin/file-centric-manifests
• aa342c1 Merge branch 'main' into juxtin/file-centric-manifests
• f86e5bf README updates for v5.0.0
• 69b8872 Update wording in error message
• e11bd00 Remove debug line
• b737283 Update version to 5.0.0 since this has breaking changes
• 3059e7f Minor tweaks
• 06796b8 Do not aggregate manifest files in multi-module projects
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[dependabot]

Looks like advanced-security/maven-dependency-submission-action is up-to-date now, so this is no longer needed.