Skip to content

chore(deps): update actions/cache action to v5 #4819

chore(deps): update actions/cache action to v5

chore(deps): update actions/cache action to v5 #4819

Triggered via push April 16, 2026 18:14
Status Success
Total duration 1m 16s
Artifacts 3
Matrix: e2e-tests
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

14 warnings
tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
tests: e2e-tests/lib/mock-backend.ts#L119
Unsafe member access .toString on an `any` value
tests: e2e-tests/lib/mock-backend.ts#L119
Unsafe call of an `any` typed value
tests: e2e-tests/lib/mock-backend.ts#L119
Unsafe call of an `any` typed value
tests: e2e-tests/lib/mock-backend.ts#L119
Unsafe assignment of an `any` value
tests: e2e-tests/lib/mock-backend.ts#L96
Promise-returning function provided to property where a void return was expected
tests: e2e-tests/lib/mock-backend.ts#L75
Computed name [fingerprint] resolves to an `any` value
tests: e2e-tests/lib/mock-backend.ts#L73
Promise-returning function provided to property where a void return was expected
tests: e2e-tests/lib/mock-backend.ts#L69
Promise-returning function provided to property where a void return was expected
tests: e2e-tests/lib/mock-backend.ts#L57
Unsafe assignment of an `any` value
tests: e2e-tests/lib/mock-backend.ts#L49
Promise-returning function provided to property where a void return was expected
e2e-tests (chromium)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@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/
e2e-tests (firefox)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@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/
e2e-tests (webkit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
playwright-report-chromium Expired
180 KB
sha256:e335ae7b215b530abc7ef9643c54b782cf2654cb2e33b6cd431c5558678ef542
playwright-report-firefox Expired
180 KB
sha256:c279d30c28a0dca0b0995058e169456790346e2dd3db96e2a90a40d7d1f18924
playwright-report-webkit Expired
870 KB
sha256:6ee57586c9875863a102bbb7f12bf44a3a2f0ba4f28b975187060a78db79a073