Skip to content

fix: migrate connections before migrate locks #767

fix: migrate connections before migrate locks

fix: migrate connections before migrate locks #767

Triggered via pull request July 24, 2024 06:13
Status Success
Total duration 16m 10s
Artifacts

test_workflows.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
checks
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
checks
The `save-state` 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/
checks
The `save-state` 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/
checks
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, golangci/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e
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/
e2e
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/setup-helm@v1, engineerd/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
e2e
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, azure/setup-helm@v1, engineerd/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/