Gradle Build Action Versions Save

Beta release of gradle-build-action@v3. Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Add dependency-graph: clear option to clear any dependency-graph previously submitted by the job
• Make it easy to publish a Build Scan® to https://scans.gradle.com (#1044)

Full Changelog: https://github.com/gradle/gradle-build-action/compare/v3.0.0-beta.4...v3.0.0-beta.5

Adds a new option to clear a previously submitted dependency-graph.

steps:
- uses: gradle/gradle-build-action@v2
  with:
    dependency-graph: clear

This may prove useful when migrating to a workflow using the upcoming gradle/actions/dependency-submission action.

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0

Beta release of gradle-build-action@v3. Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.
• Update the Gradle Enterprise injection configuration for product rename to Develocity (#995)
• Avoid submitting an empty dependency graph when state is loaded from configuration-cache
• Added dependency-graph-continue-on-failure input, which can be set to false to force the Job to fail when dependency graph submission fails (#1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (#1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (#997)
• Fix delay in post-action that was introduced when upgrading to Node 20 (#1038)

Beta release of gradle-build-action@v3. Can be referenced via gradle/[email protected] or gradle/gradle-build-action@v3-beta.

• Allow cache entries to be reused by jobs with the same ID in different workflows (#1017)
  • Workflow name remains part of the cache key, but cache entries generated by the same job id in a different workflow may be restored
• Register pre-installed JDKs in Maven toolchains.xml file (#1024)
  • This allows pre-installed JDKs to be auto-detected by Gradle Toolchain support

Beta release of gradle-build-action@v3.

• Adds support for automatic adding PR comment with Job Summary content (#1020)

First beta release of v3.x

• Support for save & restore of configuration-cache data #966
• Switch to run with NodeJs 20.x #946
• Deprecation of the arguments parameter #996

This patch release fixes an issue that prevented the gradle-build-action from executing with Gradle 1.12, and improves error reporting for dependency submission failures.

Changelog

• [FIX] Poor error reporting for dependency-submission failure #1008
• [FIX] Error with gradle-build-action v2.11.0 and Gradle 1.12: unable to resolve class PluginManager #1007

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1

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: https://github.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.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

• [NEW] Add artifact-retention-days configuration parameter #903
• [FIX] Update to v1.0.0 of the github-dependency-graph-gradle-plugin
• [FIX] Update @babel/traverse to address reported security vulnerability

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.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: https://github.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0