Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump advanced-security/maven-dependency-submission-action from 2.0.0 to 4.1.1 #6

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 5, 2024

Bumps advanced-security/maven-dependency-submission-action from 2.0.0 to 4.1.1.

Release notes

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

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.

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

New Contributors

Full Changelog: advanced-security/maven-dependency-submission-action@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

... (truncated)

Commits
  • 4f64dda chore: Updating release files
  • dba3dac 4.1.1
  • 4883574 Merge pull request #89 from david-wiggs/hotfix/fix-test
  • 33e1d3d Remove reference to undefined function
  • 4b85c77 Merge pull request #88 from david-wiggs/unique-job-matrix
  • 73d9d97 Update src/snapshot-generator.test.ts
  • 967455e No need to import getMavenSettingsFile when testing
  • 7592e88 Use supplied correlator without concatenation
  • 2ba839e Add some tests
  • 5275a08 Address merge conflicts
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

Bumps [advanced-security/maven-dependency-submission-action](https://github.com/advanced-security/maven-dependency-submission-action) from 2.0.0 to 4.1.1.
- [Release notes](https://github.com/advanced-security/maven-dependency-submission-action/releases)
- [Commits](advanced-security/maven-dependency-submission-action@571e99a...4f64dda)

---
updated-dependencies:
- dependency-name: advanced-security/maven-dependency-submission-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 5, 2024
@wolverian wolverian self-requested a review September 5, 2024 09:46
@wolverian wolverian merged commit ab03572 into main Sep 5, 2024
1 check passed
@wolverian wolverian deleted the dependabot/github_actions/advanced-security/maven-dependency-submission-action-4.1.1 branch September 5, 2024 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant