Skip to content

Upgrade react to v17 - resolve packages not match react 17 #124

Upgrade react to v17 - resolve packages not match react 17

Upgrade react to v17 - resolve packages not match react 17 #124

Triggered via pull request June 13, 2023 03:58
Status Success
Total duration 2m 30s
Artifacts

canary_release.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
canary-release
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-node@v1, actions/cache@v2, bobheadxi/deployments@v0.4.3, nyaa8/package-version@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
canary-release
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/
canary-release
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/
canary-release
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/