Skip to content
CI

Align cleanse mode recommendations with actual server format support #49

Sign in to view logs

Align cleanse mode recommendations with actual server format support

Align cleanse mode recommendations with actual server format support #49

Triggered via pull request May 18, 2026 01:40
@ChrisAdamsdevelopmentChrisAdamsdevelopment
opened #27
codex/fix-cleanse-mode-contradictions-and-account-handling
Status Failure
Total duration 26s
Artifacts 1

ci.yml

on: pull_request
Backend – audit & smoke test
16s
Backend – audit & smoke test
Frontend – type-check & build
22s
Frontend – type-check & build
Docker – build image
Docker – build image
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Backend – audit & smoke test
Process completed with exit code 1.
Backend – audit & smoke test
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/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/
Frontend – type-check & build
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/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
frontend-dist Expired
142 KB
sha256:8135c08ce8149b0e8a822c983e72b65570d03d478e2c0a902fa2d68d2d2a0b0f