chore: Update caching keys in CI workflow to reflect Node.js version 20
Some checks failed
LabFusion CI/CD Pipeline / api-gateway (push) Failing after 30s
Docker Build and Push / build-and-push (push) Failing after 40s
LabFusion CI/CD Pipeline / service-adapters (push) Successful in 52s
Integration Tests / integration-tests (push) Failing after 35s
Integration Tests / performance-tests (push) Has been skipped
LabFusion CI/CD Pipeline / frontend (push) Failing after 1m7s
LabFusion CI/CD Pipeline / api-docs (push) Successful in 1m37s
LabFusion CI/CD Pipeline / integration-tests (push) Has been skipped
Some checks failed
LabFusion CI/CD Pipeline / api-gateway (push) Failing after 30s
Docker Build and Push / build-and-push (push) Failing after 40s
LabFusion CI/CD Pipeline / service-adapters (push) Successful in 52s
Integration Tests / integration-tests (push) Failing after 35s
Integration Tests / performance-tests (push) Has been skipped
LabFusion CI/CD Pipeline / frontend (push) Failing after 1m7s
LabFusion CI/CD Pipeline / api-docs (push) Successful in 1m37s
LabFusion CI/CD Pipeline / integration-tests (push) Has been skipped
### Summary of Changes - Modified caching keys in the CI workflow configuration to use Node.js version `20` instead of `18`, ensuring proper cache management for dependencies. ### Expected Results - Improved efficiency in dependency caching during CI runs, aligning with the recent Node.js version upgrade.
This commit is contained in:
@@ -222,9 +222,9 @@ jobs:
|
|||||||
~/.npm
|
~/.npm
|
||||||
node_modules
|
node_modules
|
||||||
~/.cache/node-gyp
|
~/.cache/node-gyp
|
||||||
key: npm-${{ runner.os }}-18-${{ hashFiles('frontend/package-lock.json') }}
|
key: npm-${{ runner.os }}-20-${{ hashFiles('frontend/package-lock.json') }}
|
||||||
restore-keys: |
|
restore-keys: |
|
||||||
npm-${{ runner.os }}-18-
|
npm-${{ runner.os }}-20-
|
||||||
npm-${{ runner.os }}-
|
npm-${{ runner.os }}-
|
||||||
npm-
|
npm-
|
||||||
fail-on-cache-miss: false
|
fail-on-cache-miss: false
|
||||||
|
|||||||
Reference in New Issue
Block a user