v2.4.0

What's new

The v.2.4.0 release contains various library updates and fixes to fully support Gradle 8.

Notable changes:

• Update to @actions/cache: 3.1.3 should improve cache save/restore performance on Windows by using gnu tar and zstd when available.
• Fix caching of extracted JDK toolchains for Gradle 7.6+ (e444647)

Full Changelog: v2.3.3...v2.4.0

v2.3.3

This patch release removes all uses of the deprecated set-output and set-state commands, and should remove deprecation warnings from build logs. See #461 and #477 for more details.

Full Changelog: v2.3.2...v2.3.3

v2.3.2

This patch release fixes an issue which could result in errors in the post-action step. See #441 for details.

Full Changelog: v2.3.1...v2.3.2

v2.3.1

This patch release addresses some security vulnerabilities reported by the CodeQL check:

• Removes sourcemap-register.js: this triggered Incorrect suffix check
• Patches the @azure/logger library to avoid logging an environment variable value: this triggered Clear-text logging of sensitive information
• Updates a bunch of development dependencies, which should not impact production code

The release contains no functional changes.

Full Changelog: v2.3.0...v2.3.1

v2.3.0

What's new

With v2.3.0, the gradle-build-action can now attempt to remove any unused files from the Gradle User Home directory before storing to the GitHub Actions cache. This can prevent cases where the size of cache entry grows over time.

Gradle Home cache cleanup is disabled by default. You can enable this feature for the action as follows:

gradle-home-cache-cleanup: true

See the README for more details.

Full Changelog: v2.2.5...v2.3.0

v2.3.0-beta.1

Introduces experimental support for removing unused files from Gradle User Home prior to caching.

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