Skip to content

v0.6.0: production hardening — migrations, tiered retention, zc_statu… #1

v0.6.0: production hardening — migrations, tiered retention, zc_statu…

v0.6.0: production hardening — migrations, tiered retention, zc_statu… #1

Triggered via push March 26, 2026 14:50
Status Failure
Total duration 45s
Artifacts

ci.yml

on: push
TypeScript type check
14s
TypeScript type check
Matrix: Build, Unit Tests, Security Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Build, Unit Tests, Security Tests (22.x)
Process completed with exit code 13.
TypeScript type 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/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, Unit Tests, Security Tests (22.x)
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. 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/