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

martijnvisser pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/master by this push:
     new 44522470ec3 [hotfix] Use branch-based cache key for legacy docs 
workflow
44522470ec3 is described below

commit 44522470ec380cff4daba9d580d1e1e3577b6cac
Author: Martijn Visser <[email protected]>
AuthorDate: Wed Jan 21 19:45:25 2026 +0100

    [hotfix] Use branch-based cache key for legacy docs workflow
    
    Since legacy branches are frozen, use a simple branch-based cache key 
instead of content-based hashing. This avoids the hashFiles error while still 
providing goo cache reuse across builds.
---
 .github/workflows/docs-legacy.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/docs-legacy.yml 
b/.github/workflows/docs-legacy.yml
index 562c1d40844..3064f6391f2 100644
--- a/.github/workflows/docs-legacy.yml
+++ b/.github/workflows/docs-legacy.yml
@@ -59,9 +59,9 @@ jobs:
         uses: actions/cache@v4
         with:
           path: ~/.m2/repository
-          key: ${{ runner.os }}-maven-docs-${{ hashFiles('**/pom.xml') }}
+          key: ${{ runner.os }}-maven-docs-legacy-${{ inputs.branch }}
           restore-keys: |
-            ${{ runner.os }}-maven-docs-
+            ${{ runner.os }}-maven-docs-legacy-
 
       - name: Build Jekyll documentation (release-1.12 and earlier)
         if: ${{ contains(fromJSON('["release-1.0", "release-1.1", 
"release-1.2", "release-1.3", "release-1.4", "release-1.5", "release-1.6", 
"release-1.7", "release-1.8", "release-1.9", "release-1.10", "release-1.11", 
"release-1.12"]'), inputs.branch) }}

Reply via email to