v2.2.5

What's fixed

Fixes a bug where a corrupted cache entry caused an error in beforeSave (#408). This meant that the entry was never purged.
By allowing @actions/globber to follow symlinks and ignore broken symlinks, the bad files in the cache entry are ignored and the corrupted cache entry can be replaced by a good one.

Full Changelog: v2.2.4...v2.2.5

v2.2.4

What's fixed

The fix for #383 introduced a bug that caused the post-action to fail when attempting to resolve cache-read-only for scheduled jobs.
This has been fixed with an explicit (rather than implicit) check for 'event.repository != null'. (#409)

Full Changelog: v2.2.3...v2.2.4

v2.2.3

What's fixed

This release updates a number of key dependencies and fixes some cache-related issues:

• Do not set cache-read-only=true for scheduled workflows on default branch (#383)
• Fix reporting of caching errors that was broken in v2.2.2 (#407)
• Abort cache download operations after 10 minutes (configurable). Previously cache download operations could hang the build. (#369)

Full Changelog: v2.2.2...v2.2.3

v2.2.2

What's fixed

This release fixes some issues that were discovered in the v2.2.1 release, and updates a number of dependencies.

• Improved support for GitHub Enterprise
  • Do not attempt to use GitHub Actions cache when the feature is not available
  • Write Gradle Build summary to log files when Job Summary functionality not available
• Only attempt to stop Gradle daemons when caching Gradle User Home (#341)
• Only write build-results file when GitHub Actions env vars are available (#350)

Full Changelog: v2.2.1...v2.2.2

v2.2.1

What's fixed

This release fixes some issues that were exposed by the v2.2.0 release, as well as improving the content and layout of the Job Summary.

• Don't try to generate Job Summary when functionality is not available (GitHub Enterprise): #319
• Fix warning when attempting to delete non-existent file: #308
• Fix Entry not saved: reason unknown message in Job Summary cache details: #309
• Report failure to publish build scan in Job Summary: #326

Full Changelog: v2.2.0...v2.2.1

v2.2.0

Summary

This release brings a new Job Summary report, as well as numerous improvements and bug fixes:

• Capture all Gradle build executions for a job and write them to the GitHub Actions Job Summary.
• Default to cache-read-only for non-default branches (see 0a36ca9)
• Allow the Gradle Daemon to run across build steps in a workflow Job (see #113)

Issues resolved

https://github.com/gradle/gradle-build-action/milestone/7?closed=1

What's Changed

• Use GHA Job Summary to summarize Gradle build results by @bigdaz in #282
• Various improvements to CI workflows by @bigdaz in #294
• Extract init scripts and state tracking by @bigdaz in #297
• Add improved Job Summary with build results and caching report by @bigdaz in #298
• Fix save/restore of configuration-cache by @bigdaz in #302
• Improve layout and formatting of Job Summary by @bigdaz in #303
• Default to cache-read-only for non-default branches by @bigdaz in #149
• Improve init scripts and add test coverage by @bigdaz in #304
• Allow daemons to run across workflow steps by @bigdaz in #305
• Use java to determine user.home dir by @bigdaz in #306

Full Changelog: v2.1.7...v2.2.0

v2.2.0-rc.2

Wait a bit longer and report failures better for file locking issues: 8096e65

v2.2.0-rc.1

First RC of v2.2.0 release. See v2.2.0 closed issues for details.

v2.1.7

Fixes #293, which prevented v2.1.6 from allowing Gradle to re-use previously downloaded wrapper distributions. This slowed down build executions and could result in build flakiness when the wrapper zip failed to download.

• [FIX] Retain more items in the wrapper folder of Gradle User Home, avoiding re-download of wrapper distributions.

v2.2.0-beta.1

First cut at using GHA Job Summary to display Gradle Build results