(polaris) branch main updated: Revert update gradle/actions action to v5 (#4518)

[sn...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

snazy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git


The following commit(s) were added to refs/heads/main by this push:
     new 382613adac Revert update gradle/actions action to v5 (#4518)
382613adac is described below

commit 382613adac5c0b8e482c0392ef5b9a8b728633fd
Author: Robert Stupp <sn...@snazy.de>
AuthorDate: Tue May 26 08:31:28 2026 +0200

    Revert update gradle/actions action to v5 (#4518)
    
    This reverts #4512, commit e7ebe8dab2a67c4db908d1f73c222efd18d2a7cf.
    
    Version 6 of gradle/actions changes the licensing model for the default caching behavior used by setup-gradle.
    The action repository is still mostly MIT licensed, but the default "enhanced" caching provider uses the [proprietary gradle-actions-caching](https://github.com/gradle/actions/blob/v6.1.0/licenses/gradle-actions-caching-license.txt) component.
    
    Gradle [documents](https://github.com/gradle/actions/blob/v6.1.0/DISTRIBUTION.md#3-usage-tiers) enhanced caching for public repositories as free, and private repository use as currently available in a free preview.
    The same documentation also says Gradle plans usage-based pricing for undefined "large-scale commercial organizations".
    Use of the proprietary caching component is governed by [Gradle's Terms of Use](https://gradle.com/legal/gradle-technologies-terms-of-use/), which may change over time.
    
    Version 6 also provides an opt-in ["basic"](https://github.com/gradle/actions/blob/v6.1.0/docs/setup-gradle.md#basic-caching) caching provider under the MIT license, but it is not equivalent to the default enhanced provider.
    Basic caching uses actions/cache directly and lacks [enhanced](https://github.com/gradle/actions/blob/v6.1.0/docs/setup-gradle.md#enhanced-caching) caching's fine-grained Gradle User Home caching, intelligent cleanup, deduplication, or restore-key behavior.
    For Polaris CI, especially the incremental cache workflow, that would likely mean lower cache reuse and more cache growth over time.
    
    This is difficult for Polaris because contributors may run CI in private repositories, including private forks used for security work.
    With v6 defaults, those workflows would depend on proprietary, mutable terms whose future private repository terms and limits are not yet defined.
    Switching v6 to basic caching avoids the proprietary component, but gives up caching behavior that the workflow currently relies on.
    
    Revert to v5 so the workflow avoids v6's proprietary enhanced caching provider without regressing to the reduced basic caching provider while we decide on a longer-term approach.
---
 .github/actions/ci-incr-build-cache-prepare/action.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/actions/ci-incr-build-cache-prepare/action.yml b/.github/actions/ci-incr-build-cache-prepare/action.yml
index 6d23fdce13..2fe3ca2c22 100644
--- a/.github/actions/ci-incr-build-cache-prepare/action.yml
+++ b/.github/actions/ci-incr-build-cache-prepare/action.yml
@@ -71,7 +71,7 @@ runs:
         fi
 
     - name: Gradle / Setup
-      uses: gradle/actions/setup-gradle@50e97c2cd7a37755bbfafc9c5b7cafaece252f6e # v6
+      uses: gradle/actions/setup-gradle@0723195856401067f7a2779048b490ace7a47d7c # v5
       with:
         cache-read-only: ${{ inputs.cache-read-only }}
         validate-wrappers: false