ci: 🤖 Update test matrix with new releases (05/18) #8363
alexander-alderman-webbtest-integrations-flags.yml
on: pull_request
Matrix: Flags
All Flags tests passed
3s
Annotations
7 warnings
|
Flags (3.7, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.10, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.8, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.12, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.14t, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.14, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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/
|
|
Flags (3.13, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. 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 | |
|---|---|---|---|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
119 KB |
sha256:0b3505af2f122a9a39e08381bbf98edbc09efb79aeba9cdf089c1d9c04221be8
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
120 KB |
sha256:26bb0ddd5af3c926df87aa4672456b9611d88453eb0b0d241f7854d09d7615c2
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
119 KB |
sha256:55b1fa10373d296d21536aad2e7ada31d8950e6563eb653b177280b3d9d027b4
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
120 KB |
sha256:01739f4a757660bf0a8e72a2ff5da607eb5da48d81a4cc14103e00a3bad987fe
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
120 KB |
sha256:c64878b22d08e5e4b43c65135ede9911f86c27259670188d8a38dc5d867bde81
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
120 KB |
sha256:0a6b5025e0baa30616c886362347728d4265c9528346725287fc8a326c0f98b8
|
|
|
codecov-coverage-results-toxgen-update-05-18-test-flags
|
120 KB |
sha256:7c16c13f571002545610a4252d00f41a9f6f1cb6fac03166bfe7032739d991a6
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
230 Bytes |
sha256:04073be92808a1be32a56792f74ed169890ea028d9a6fae5b1c9f126b4a499eb
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
229 Bytes |
sha256:01a5fba19f879ad06ff8998446c3b87d8bc76ff7642e7a27db1a44a80d2cfdaa
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
230 Bytes |
sha256:6daaf39900e24749320bf46c454c31aa1167f05650b538cd2c70b72b73aa8089
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
231 Bytes |
sha256:61693f4565354272f753d221df988341587a1be6439bb4297d0b04ca81a987a2
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
230 Bytes |
sha256:c0fbaa57816da8df536f33724cebf72e608807c1389d45de28f3f808b71a1bf4
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
231 Bytes |
sha256:dd5570010dcc1fab233a5f49b8529eaaac73e682a6c1540ab2d2f48c5c76446a
|
|
|
codecov-test-results-toxgen-update-05-18-test-flags
|
230 Bytes |
sha256:49eb55d00932ae1da97a3aab483fd548b5b770b7478d6a49cf77a289f1c8c562
|
|