Today, we’re releasing v6 of GitHub Actions for Gradle builds, with an important change to how the caching component is licensed. In this blog post, we explain what’s changing, what it means for you, and where we’re headed.

Gradle Blog

Gradle Inc is releasing v6 of GitHub Actions for Gradle builds, with a key licensing change: the caching component of `setup-gradle` has been extracted into a closed-source library (`gradle-actions-caching`) distributed under Gradle's Terms of Use. No functional restrictions are introduced in this release — workflows continue to work as before. The only functional change is removal of experimental Configuration Cache support, which is being reworked. Caching will remain free for public repositories. The change is motivated by the engineering investment required to maintain and advance caching infrastructure, with future premium capabilities planned such as production-ready Configuration Cache support and improved performance for self-hosted runners.

GitHub Actions for Gradle v6: What's Changing and Why