Releases: advanced-security/maven-dependency-submission-action
Releases · advanced-security/maven-dependency-submission-action
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 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.3
The release bumps dependency versions to stay up-to-date.
v4.1.2
v4.1.1
chore: Updating release files
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
v4.0.2
chore: Updating release files
v4.0.1
- Updating branding for the marketplace
- Utilizing rollup to build cli executables as the ESM module for the
dependency-submission-toolkit
broke the4.0.0
pkg
based executable builds.
v4.0.0
Version 4.0.0 release:
- Breaking change, the name presented in the submission report now matches the current name of the repository
maven-dependency-submission-action
(previously it was moved from a repository calledmaven-dependency-tree-action
) - When running the GitHub Action the
ref
andsha
are injected as inputs (with defaults to the current workflow values) - Updated dependencies, specifically
dependency-submission-toolkit
that includes improvements to uploading of the snapshots and error handling around unhappy path scenarios - CLI application options made compatible with the GitHub Actions inputs
- CLI applications made available as part of the release process and notes
- Project testing and releases - swapped
jest
out forvitest
and added GitHub Actions release workflow
v3.0.3
- Fixes issue with POMs that set a non-default
outputDirectory
resulting is no dependency data being found and uploaded #48.