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.
Highlights
🆕 Fetch additional metadata about Dependabot commits
You can now optionally enable API lookups within the Action to retrieve extra information about Dependabot PRs.
Example:
The flags enable the following new outputs:
steps.dependabot-metadata.outputs.alert-state
alert-lookup
istrue
, this contains the current state of that alert (OPEN, FIXED or DISMISSED).steps.dependabot-metadata.outputs.ghsa-id
alert-lookup
istrue
, this contains the GHSA-ID of that alert.steps.dependabot-metadata.outputs.cvss
alert-lookup
istrue
, this contains the CVSS value of that alert (otherwise it contains 0).steps.dependabot-metadata.outputs.compatibility-score
compat-lookup
istrue
, this contains the compatibility score (otherwise it contains 0).Many thanks to @mwaddell for contributing these additional flags 🥇
The Action no longer fails if other commits are present
We received feedback at this change was highly obtrusive and blocking common workflows that merging in the target branch. Following on from changes in 1.2.1 to make it easier for a user to re-run failed workflows this friction was much more obvious.
Thanks for the feedback, and thanks @mwaddell for contributing the change.
The Action defaults to using the GITHUB_TOKEN
This makes us consistent with other GitHub Actions such as
actions/checkout
in using the baseline token provided to the workflow. Since the Action doesn't have any features which require write scopes this defaulting is adequate for all use cases.Thanks @jablko for contributing this change 🏆
What's Changed
bump-version
to update README.md as well by @mwaddell in Updatedbump-version
to update README.md as well #163New Contributors
Full Changelog: v1.2.1...v1.3.0