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

ci(deps): bump gradle/gradle-build-action from 2.10.0 to 2.11.0 #76

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 12, 2023

Bumps gradle/gradle-build-action from 2.10.0 to 2.11.0.

Release notes

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

v2.11.0

In addition to a number of dependency updates, this release:

  • Allows a custom Plugin Repository to be specified when resolving the github-dependency-graph-gradle-plugin. See the documentation for details.
  • Brings increased resilience when failures occur collecting build results or cleaning the Gradle User Home. Such failures should no longer prevent the caching of Gradle User Home or lead to build failures.

Changelog

  • [NEW] Allow a custom plugin repository to be used to resolve dependency-graph plugin #933
  • [FIX] Cache entries and Job Summary not written on cache-cleanup failure #990 #858
  • [FIX] Failure to write build results file should not cause overall build to fail #866

Full-changelog: gradle/gradle-build-action@v2.10.0...v2.11.0

Commits
  • 8cbcb99 Plugin repository URL is configurable
  • a71aff6 Handle failure in cache-cleanup
  • 77699ba Handle failure writing build-results file
  • dc59272 Merge branch 'dd/dependency-updates'
  • 4f0075d Clarify docs for dedicated workflow
  • e1f9864 Bumps the npm-dependencies group with 5 updates:
  • 76d5a9b Bump the github-actions group with 2 updates
  • 39d8c6d Bump from Gradle 8.4 to Gradle 8.5
  • 0280eb7 docs: upload build reports even when build failed
  • See full diff 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 [gradle/gradle-build-action](https://github.com/gradle/gradle-build-action) from 2.10.0 to 2.11.0.
- [Release notes](https://github.com/gradle/gradle-build-action/releases)
- [Commits](gradle/gradle-build-action@v2.10.0...v2.11.0)

---
updated-dependencies:
- dependency-name: gradle/gradle-build-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Copy link
Contributor

Qodana Community for JVM

2 new problems were found

Inspection name Severity Problems
Unstable API Usage 🔶 Warning 1
Unused symbol 🔶 Warning 1

💡 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 and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format 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:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.3.0
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

@nekofar nekofar merged commit b85fdc4 into develop Dec 13, 2023
7 checks passed
@nekofar nekofar deleted the dependabot/github_actions/develop/gradle/gradle-build-action-2.11.0 branch December 13, 2023 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant