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

• 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

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 the 4.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 called maven-dependency-tree-action)
• When running the GitHub Action the ref and sha 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 for vitest 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.

v3.0.2

What's Changed

• Make action GHES compatible by @cnagadya in #40

New Contributors

• @cnagadya made their first contribution in #40

Full Changelog: v3...v3.0.2

v3.0.1

• Updated to latest dependency snapshot library 1.2.10
• Fixed error in the cli tools that was incorrectly validating the branch specification #26
• Correctly injecting the additional maven command line options #28

v3.0.0

• Introduced support for maven multi module project, reporting as an aggregation on the top level POM
• Added support for maven wrapper if provided in the project
• Improved reporting and modification of the path to the POM file so as to be a correct link in dependency graph
• Fixed the bug reported in #19 by using more parts of the Maven coordinate system to guarantee uniqueness on the PackageURLs for the dependencies, i.e. the type and classifier are now supported if specified.