chore(deps): update actions/cache action to v5 #4798
test-and-release.yaml
on: push
Matrix: e2e-tests
tests
50s
release
0s
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:6cf5d56312ecab69a5fb47623734e4afa03266380e810a62e487c5fd2f142b88
|
|
|
playwright-report-firefox
Expired
|
180 KB |
sha256:3faae81ac0f32efdff361a2c37eab2725e4928d7ecb61cbf3e3a799eaac2b68c
|
|
|
playwright-report-webkit
Expired
|
180 KB |
sha256:cbf00be05fcd0f4ba6732ffc6b6b83d262a2be947be937c53564f6f48d2a6bf3
|
|