Bumps gradle/gradle-build-action from 2.6.0 to 2.7.0.

Release notes

Sourced from gradle/gradle-build-action's releases.

v2.7.0

GitHub Dependency Graph support

In this release, the GitHub Dependency Graph support is no longer considered "experimental", and should be considered ready for production use. You can read more about the Dependency Graph support in the README chapter.

Changes

  • Update to github-dependency-graph-gradle-plugin@v0.2.0
    • Dependency graph uses Gradle Settings file as manifest location (if Settings file exists)
  • Adds a dependency-graph-file output to any step that generates a Dependency Graph file

Changelog

https://github.com/gradle/gradle-build-action/compare/v2.6.1...v2.7.0

v2.6.1

Dependency Graph support

This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support:

  • The action will now generate a unique job.correlator value for each Gradle invocation within a Job. This permits multiple Gradle invocations in a single job to generate and submit a separate dependency graph.
  • Update to use github-dependency-graph-gradle-plugin@v0.1.0, which brings a number of improvements to the generated dependency graph:
    • Each Gradle build invocation is mapped to a single GitHub Dependency Graph manifest. This should result in fewer duplicate security alerts being generated.
    • Configurations that contribute to the GitHub Dependency Graph can be filtered by regular expression
Commits
  • a4cf152 Merge pull request #817 from gradle/dd/270
  • a8aac05 Build outputs
  • 7241fa5 Add new output to Action.yml
  • 9e58f8b Add dependency-graph-file as step output
  • 632e888 Update to the latest dependency-graph plugin
  • ced6859 Update Build Scan™ to Build Scan®
  • 0904709 Bump GE plugin versions
  • 1b94073 Bump development dependencies
  • 4821f54 Group all npm dependencies in a single dependabot PR
  • 2dbad1e Bump the github-actions group with 1 update
  • 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 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)

Comment From: dependabot[bot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.