Skip to content

[General Usage]: How to stop replacing schema while migrating #6350

[General Usage]: How to stop replacing schema while migrating

[General Usage]: How to stop replacing schema while migrating #6350

Triggered via issue October 4, 2024 05:43
Status Success
Total duration 11s
Artifacts

ok-to-test.yml

on: issue_comment
ok-to-test
2s
ok-to-test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
ok-to-test
The following actions uses node12 which is deprecated and will be forced to run on node16: chanzuckerberg/[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/
ok-to-test
The following actions use a deprecated Node.js version and will be forced to run on node20: chanzuckerberg/[email protected], peter-evans/slash-command-dispatch@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ok-to-test
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/