fix(security): GA-021/022 download timeout and checksum fail-closed #115
ci.yml
on: pull_request
Matrix: test
security
14s
build
0s
Annotations
8 errors and 3 warnings
|
test (20.x)
Process completed with exit code 1.
|
|
tests/unit/checksum.test.ts > Checksum verification > should accept CAPISCIO_REQUIRE_CHECKSUM values: 1, yes, TRUE:
tests/unit/checksum.test.ts#L260
AssertionError: expected [Function] to throw error including 'Checksum verification required' but got 'Checksum verification failed: checksu…'
Expected: "Checksum verification required"
Received: "Checksum verification failed: checksums.txt is not available. Cannot verify binary integrity. Set CAPISCIO_SKIP_CHECKSUM=true to bypass."
❯ tests/unit/checksum.test.ts:260:7
|
|
tests/unit/checksum.test.ts > Checksum verification > should skip verification when asset not found in checksums.txt and require is off:
tests/unit/checksum.test.ts#L228
AssertionError: promise rejected "Error: Checksum verification failed: asse…" instead of resolving
❯ tests/unit/checksum.test.ts:228:42
Caused by: Caused by: Error: Checksum verification failed: asset capiscio-linux-amd64 not found in checksums.txt. Set CAPISCIO_SKIP_CHECKSUM=true to bypass.
❯ BinaryManager.verifyChecksum src/utils/binary-manager.ts:206:13
❯ BinaryManager.install src/utils/binary-manager.ts:137:7
❯ BinaryManager.getBinaryPath src/utils/binary-manager.ts:96:7
❯ tests/unit/checksum.test.ts:228:5
|
|
tests/unit/checksum.test.ts > Checksum verification > should throw when checksums.txt fetch fails and CAPISCIO_REQUIRE_CHECKSUM=true:
tests/unit/checksum.test.ts#L191
AssertionError: expected [Function] to throw error including 'Checksum verification required' but got 'Checksum verification failed: checksu…'
Expected: "Checksum verification required"
Received: "Checksum verification failed: checksums.txt is not available. Cannot verify binary integrity. Set CAPISCIO_SKIP_CHECKSUM=true to bypass."
❯ tests/unit/checksum.test.ts:191:5
|
|
tests/unit/checksum.test.ts > Checksum verification > should skip verification when checksums.txt fetch fails and CAPISCIO_REQUIRE_CHECKSUM is not set:
tests/unit/checksum.test.ts#L179
AssertionError: promise rejected "Error: Checksum verification failed: chec…" instead of resolving
❯ tests/unit/checksum.test.ts:179:42
Caused by: Caused by: Error: Checksum verification failed: checksums.txt is not available. Cannot verify binary integrity. Set CAPISCIO_SKIP_CHECKSUM=true to bypass.
❯ BinaryManager.verifyChecksum src/utils/binary-manager.ts:194:13
❯ BinaryManager.install src/utils/binary-manager.ts:137:7
❯ BinaryManager.getBinaryPath src/utils/binary-manager.ts:96:7
❯ tests/unit/checksum.test.ts:179:5
|
|
security
Process completed with exit code 1.
|
|
test (18.x)
The strategy configuration was canceled because "test._20_x" failed
|
|
test (18.x)
The operation was canceled.
|
|
test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
security
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (18.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|