Skip to content

[WRSAT-511] Fixing PDF other/additional info mappings (#216) #226

[WRSAT-511] Fixing PDF other/additional info mappings (#216)

[WRSAT-511] Fixing PDF other/additional info mappings (#216) #226

Triggered via push April 10, 2026 22:00
Status Failure
Total duration 7m 24s
Artifacts
Deploy to staging  /  ...  /  scan_ruby
13s
Deploy to staging / Verify code is valid / scan_ruby
Deploy to staging  /  ...  /  lint
12s
Deploy to staging / Verify code is valid / lint
Deploy to staging  /  ...  /  check_migrations
3m 17s
Deploy to staging / Verify code is valid / check_migrations
Deploy to staging  /  ...  /  test
3m 18s
Deploy to staging / Verify code is valid / test
Deploy to staging  /  Deploy to staging
3m 55s
Deploy to staging / Deploy to staging
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Deploy to staging / Deploy to staging
Deployment workflow completed with stats: failure
Deploy to staging / Verify code is valid / lint
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/