Bump gradle/gradle-build-action from 2.6.1 to 2.7.0

[dependabot[bot]]

Bumps gradle/gradle-build-action from 2.6.1 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

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
• See full diff in compare view

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)

[codecov[bot]]

Codecov Report

Merging #82 (a1cf45f) into main (5a9c878) will not change coverage. The diff coverage is n/a.

@@          Coverage Diff          @@
##            main     #82   +/-   ##
=====================================
  Coverage   3.13%   3.13%           
=====================================
  Files         29      29           
  Lines        543     543           
  Branches      33      33           
=====================================
  Hits          17      17           
  Misses       525     525           
  Partials       1       1           

[github-actions[bot]]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.2.1 with: upload-result: true ```

Contact Qodana team

Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions