Skip to content

fix: env

fix: env #999

Triggered via push November 14, 2024 14:46
Status Success
Total duration 3m 51s
Artifacts

main.yml

on: push
Test backend
56s
Test backend
Build for dev env
1m 11s
Build for dev env
Build for prod env
1m 38s
Build for prod env
Deploy to new account
51s
Deploy to new account
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test backend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy to new account
The following actions uses node12 which is deprecated and will be forced to run on node16: chrnorm/deployment-action@releases/v1, chrnorm/deployment-status@releases/v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy to new account
The following actions use a deprecated Node.js version and will be forced to run on node20: chrnorm/deployment-action@releases/v1, chrnorm/deployment-status@releases/v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy to new account
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/