[FIX][CI] cache-hit incorrectly computed (#9603)

## Introduction
The `cache-hit` value should be a string boolean, but it seems like not
to always be the case ?

## Related runs
- twenty-server first attempt saves cache second retrieves it
https://github.com/twentyhq/twenty/actions/runs/12768260350
- twenty-front
https://github.com/twentyhq/twenty/actions/runs/12767064201
This commit is contained in:
Paul Rastoin
2025-01-14 14:18:33 +01:00
committed by GitHub
parent 4719fe6ed9
commit b815de3e26

View File

@ -11,7 +11,7 @@ outputs:
value: ${{ steps.restore-cache.outputs.cache-primary-key }}
cache-hit:
description: String bool indicating whether cache has been directly or indirectly hit
value: ${{ steps.restore-cache.outputs.cache-hit != 'false' || steps.restore-cache.outputs.cache-matched-key != '' }}
value: ${{ steps.restore-cache.outputs.cache-hit == 'true' || steps.restore-cache.outputs.cache-matched-key != '' }}
runs:
using: composite
@ -20,11 +20,11 @@ runs:
uses: actions/cache/restore@v4
id: restore-cache
with:
key: ${{ inputs.key }}-${{ github.ref_name }}-${{ github.sha }}
restore-keys: ${{ inputs.key }}-${{ github.ref_name }}-
path: |
.cache
.nx/cache
node_modules/.cache
packages/*/node_modules/.cache
${{ inputs.additional-paths }}
key: ${{ inputs.key }}-${{ github.ref_name }}-${{ github.sha }}
restore-keys: ${{ inputs.key }}-${{ github.ref_name }}-
${{ inputs.additional-paths }}