Skip to content

FEDX-5172: Detect build readiness from webdev stdout #59

FEDX-5172: Detect build readiness from webdev stdout

FEDX-5172: Detect build readiness from webdev stdout #59

Triggered via pull request April 1, 2026 15:38
Status Failure
Total duration 44s
Artifacts 1

ci.yaml

on: pull_request
checks  /  analyze-additional-checks
0s
checks / analyze-additional-checks
build  /  sbom
19s
build / sbom
checks  /  analyze
24s
checks / analyze
checks  /  format
16s
checks / format
checks  /  dependency-validator
27s
checks / dependency-validator
checks  /  check-release-notes
6s
checks / check-release-notes
Matrix: test-unit
Matrix: checks / additional-checks
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
checks / check-release-notes
Process completed with exit code 1.
checks / check-release-notes
Add a new entry to the 'Unreleased' section, or add an 'ignore release notes' label to this PR
checks / check-release-notes
No changes to CHANGELOG.md detected.
checks / format
Process completed with exit code 1.
checks / check-release-notes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3.0.2. 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/
checks / format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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/
build / sbom
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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/
checks / analyze
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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/
checks / dependency-validator
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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-unit (2.19.6) / dev
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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-unit (stable) / dev
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@v1. 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
webdev_proxy-sbom.cyclonedx.json Expired
6.67 KB
sha256:bcdcfde73a2db9c091824db9b2dd709708ceb7a247eb93dff530afeadf30e1ba