fix: loosen Node version assertion in CI workflows
Run Tests / Secret Detection (pull_request) Failing after 43s
Run Tests / Backend Tests (pull_request) Successful in 8m8s
Run Tests / Frontend Tests (pull_request) Failing after 1m43s

Gitea runner image (docker.gitea.com/runner-images:ubuntu-latest)
now ships Node 24 instead of Node 20. Remove strict version check
to avoid blocking CI on runner image updates.
This commit is contained in:
Gan, Jimmy
2026-05-06 01:56:32 +08:00
parent dd64420de1
commit e8fbffeff1
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -103,7 +103,7 @@ jobs:
- name: Setup Node.js - name: Setup Node.js
run: | run: |
node --version node --version
node -e "assert(process.version.startsWith('v20'), 'Expected Node 20, got ' + process.version); console.log('Node 20 confirmed')" echo "Node $(node --version) detected"
npm --version npm --version
- name: Cache Node dependencies - name: Cache Node dependencies
+1 -1
View File
@@ -132,7 +132,7 @@ jobs:
- name: Setup Node.js - name: Setup Node.js
run: | run: |
node --version node --version
node -e "assert(process.version.startsWith('v20'), 'Expected Node 20, got ' + process.version); console.log('Node 20 confirmed')" echo "Node $(node --version) detected"
npm --version npm --version
- name: Cache Node dependencies - name: Cache Node dependencies