Skip to content

chore: fix conflicts #1398

chore: fix conflicts

chore: fix conflicts #1398

Triggered via push July 30, 2024 11:43
Status Success
Total duration 4m 39s
Artifacts

sync-qa.yml

on: push
Deploy to QA server
4m 27s
Deploy to QA server
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Deploy to QA server
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1, actions/cache@v2, 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 QA server
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v1, actions/cache@v2, 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 QA server
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/20***-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Deploy to QA server
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/20***-10-11-github-actions-deprecating-save-state-and-set-output-commands/