Skip to content

fix(middleware): clean pipeline warnings and improve portability #4

fix(middleware): clean pipeline warnings and improve portability

fix(middleware): clean pipeline warnings and improve portability #4

Triggered via push March 31, 2026 06:29
Status Success
Total duration 19m 4s
Artifacts
Matrix: build-test-sanitized
Runtime Smoke Checks
3m 14s
Runtime Smoke Checks
Static Analysis
3m 17s
Static Analysis
Valgrind Checks
4m 2s
Valgrind Checks
Standalone Package Export Check
1m 57s
Standalone Package Export Check
Configuration Coverage
12m 42s
Configuration Coverage
Middleware Strict CI Summary
2s
Middleware Strict CI Summary
Fit to window
Zoom out
Zoom in

Annotations

41 warnings
Sanitized Build and Tests (clang, utils=AUTO, json=OFF)
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 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/
Sanitized Build and Tests (clang, utils=AUTO, json=OFF)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (clang, utils=OFF, json=OFF)
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 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/
Sanitized Build and Tests (clang, utils=OFF, json=OFF)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (gcc, utils=OFF, json=AUTO)
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 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/
Sanitized Build and Tests (gcc, utils=OFF, json=AUTO)
Some tests failed or no tests were discovered.
Standalone Package Export Check
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 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/
Runtime Smoke Checks
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 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/
Runtime Smoke Checks
Non-zero exit status from build-runtime/tests/middleware_csrf_smoke_test (status=134)
Runtime Smoke Checks
Non-zero exit status from build-runtime/core/template/examples/template_render_file (status=134)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/update.sample (status=1)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/sendemail-validate.sample (status=1)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/push-to-checkout.sample (status=1)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/pre-merge-commit.sample (status=2)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/pre-applypatch.sample (status=2)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/fsmonitor-watchman.sample (status=255)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/hooks/applypatch-msg.sample (status=2)
Runtime Smoke Checks
Non-zero exit status from build-runtime/_deps/vix_net-src/.git/description (status=127)
Valgrind Checks
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 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/
Valgrind Checks
Valgrind reported issues for build-valgrind/core/template/tests/template_cache_test
Valgrind Checks
Valgrind reported issues for build-valgrind/core/template/examples/template_render_file
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/update.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/sendemail-validate.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/push-to-checkout.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/pre-merge-commit.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/pre-applypatch.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/fsmonitor-watchman.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/hooks/applypatch-msg.sample
Valgrind Checks
Valgrind reported issues for build-valgrind/_deps/vix_net-src/.git/description
Configuration Coverage
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 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/
Sanitized Build and Tests (clang, utils=OFF, json=AUTO)
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 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/
Sanitized Build and Tests (clang, utils=OFF, json=AUTO)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (gcc, utils=AUTO, json=OFF)
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 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/
Sanitized Build and Tests (gcc, utils=AUTO, json=OFF)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (gcc, utils=AUTO, json=AUTO)
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 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/
Sanitized Build and Tests (gcc, utils=AUTO, json=AUTO)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (gcc, utils=OFF, json=OFF)
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 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/
Sanitized Build and Tests (gcc, utils=OFF, json=OFF)
Some tests failed or no tests were discovered.
Sanitized Build and Tests (clang, utils=AUTO, json=AUTO)
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 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/
Sanitized Build and Tests (clang, utils=AUTO, json=AUTO)
Some tests failed or no tests were discovered.
Static Analysis
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 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/