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

build(deps): bump gradle/gradle-build-action from 2.4.2 to 2.10.0 #1277

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 27, 2023

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

Release notes

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

v2.10.0

This release introduces a new artifact-retention-days parameter, which allows a user to configure how long the generated dependency-graph artifacts are retained by GitHub Actions. Adjusting the retention period can be useful to reduce storage costs associated with these dependency-graph artifacts.

See the documentation for more details.

Changelog

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

v2.9.0

The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the dependency-review-action.

See the documentation for detailed examples.

Changelog

  • [FIX] Use correct SHA for pull-request events #882
  • [FIX] Avoid generating dependency graph during cache cleanup #905
  • [NEW] Improve warning on failure to submit dependency graph
  • [NEW] Compatibility with GitHub dependency-review-action #879

Full-changelog: gradle/gradle-build-action@v2.8.1...v2.9.0

v2.8.1

Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.

Fixes

  • Incorrect endpoint used to submit Dependency Graph on GitHub Enterprise #885

Changelog

gradle/gradle-build-action@v2.8.0...v2.8.1

v2.8.0

The v2.8.0 release of the gradle-build-action introduces an easy mechanism to connect to Gradle Enterprise, as well improved support for self-hosted GitHub Actions runners.

Automatic injection of Gradle Enterprise connectivity

It is now possible to connect a Gradle build to Gradle Enterprise without changing any of the Gradle project sources. This is achieved through Gradle Enterprise injection, where an init-script will apply the Gradle Enterprise plugin and associated configuration.

This feature can be useful to easily trial Gradle Enterprise on a project, or to centralize Gradle Enterprise configuration for all GitHub Actions workflows in an organization.

See Gradle Enterprise injection in the README for more info.

Restore Gradle User Home when directory already exists

Previously, the Gradle User Home would not be restored if the directory already exists. This wasn't normally an issue with GitHub-hosted runners, but limited the usefulness of the action for persistent, self-hosted runners.

This behaviour has been improved in this release:

... (truncated)

Commits
  • 87a9a15 Use 1.0.0 release of dependency graph plugin
  • 3754817 Document artifact-retention-days
  • beff1c5 Update dev dependencies
  • 21a3ebb Bump com.fasterxml.jackson.dataformat:jackson-dataformat-smile
  • a5be560 Bump the github-actions group with 2 updates
  • 9bca466 Make artifact retention configurable
  • f757bcf Merge pull request #951 from gradle/dd/v2.9.1
  • 8b6c211 Bump to RC of github dependency graph plugin
  • 8db1c76 Build outputs
  • 6eaacfc Update NPM dependencies
  • 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 [gradle/gradle-build-action](https://github.com/gradle/gradle-build-action) from 2.4.2 to 2.10.0.
- [Release notes](https://github.com/gradle/gradle-build-action/releases)
- [Commits](gradle/gradle-build-action@749f47b...87a9a15)

---
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>
@dependabot dependabot bot added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Nov 27, 2023
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 13, 2023

Superseded by #1286.

@dependabot dependabot bot closed this Dec 13, 2023
@dependabot dependabot bot deleted the dependabot/github_actions/gradle/gradle-build-action-2.10.0 branch December 13, 2023 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants