-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecation Warning Output from GitHub Actions #959
Comments
I'm using github pages. The |
Hi @cyhcyh, this is expected as we're beginning to deprecate those workflow and started updating actions with a fix. We're back-porting that fix to checkout@v2 shortly to solve this for people that don't have control over the version of checkout that is being used, I'll report here as soon as that's done! |
That's great! Thank you! |
|
@rentziass still seeing this:
I even tried being explicit with |
@davetapley you need to use 3+ for that: https://github.com/actions/checkout/releases/tag/v3.0.0 2.5.0 was just a maintenance release for those who are still on v2 as far as I understand it. |
As I understand this is now fixed for both
@rentziass close as completed? |
That's correct, thanks for the help @TWiStErRob! Closing now. |
### What changes were proposed in this pull request? Upgrade action/checkout to v3 (point ot v3.1 now). ### Why are the changes needed? - https://github.com/actions/checkout/releases/tag/v3.1.0 cleanup "[The 'set-output' command is deprecated and will be disabled soon.](actions/checkout#959 (comment))" - https://github.com/actions/checkout/releases/tag/v3.0.0 since v3, use the node 16 to cleanup "[Node.js 12 actions are deprecated](https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/)" According to actions/checkout#959 (comment), v2.5 also address 'set-output' warning, but only v3 support node 16, so we upgrade to v3.1 rather than v2.5 ### Does this PR introduce _any_ user-facing change? No, dev only ### How was this patch tested? CI passed Closes #38322 from Yikun/checkout-v3. Authored-by: Yikun Jiang <yikunkero@gmail.com> Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
@rentziass I'm still getting this warning from action/checkout v2.5.0 |
@theofficialgman I think you're better off creating a new issue with detail (screenshot, link, yml, logs). |
I can confirm v2.5.0 still seems to trigger the deprecation warning. Upgrading to v3.1.0 fixed it for me though. |
I am seeing the same issue in our repository. With |
There are two different deprecation warning messages. The original one from this issue was about The other deprecation warning message "Node.js 12 actions are deprecated." mentioned by @davetapley is not fixed in
Lines 74 to 77 in e2f20e6
So, if you want to stop the "Node.js 12 actions are deprecated." warning from appearing, you need to update to |
### What changes were proposed in this pull request? Upgrade action/checkout to v3 (point ot v3.1 now). ### Why are the changes needed? - https://github.com/actions/checkout/releases/tag/v3.1.0 cleanup "[The 'set-output' command is deprecated and will be disabled soon.](actions/checkout#959 (comment))" - https://github.com/actions/checkout/releases/tag/v3.0.0 since v3, use the node 16 to cleanup "[Node.js 12 actions are deprecated](https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/)" According to actions/checkout#959 (comment), v2.5 also address 'set-output' warning, but only v3 support node 16, so we upgrade to v3.1 rather than v2.5 ### Does this PR introduce _any_ user-facing change? No, dev only ### How was this patch tested? CI passed Closes apache#38322 from Yikun/checkout-v3. Authored-by: Yikun Jiang <yikunkero@gmail.com> Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
I'm using |
Since this issue was already resolved in I suggest to re-run your action with Here is an example log output from using an older version of another action:
|
## Description Support for Ubuntu 18 in Github Actions is deprecated and will be removed altogether in April 2023 - so this PR updates the CI workflow to us Ubuntu 22 - an LTS release with several more years of support at minimum. This change also updates the use of `actions/checkout` to `@v3` - which addresses a deprecation warning around an outdated Node version usage under-the-hood. ## Related links - https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/ - actions/checkout#959
## Description Support for Ubuntu 18 in Github Actions is deprecated and will be removed altogether in April 2023 - so this PR updates the CI workflow to us Ubuntu 22 - an LTS release with several more years of support at minimum. This change also updates the use of `actions/checkout` to `@v3` - which addresses a deprecation warning around an outdated Node version usage under-the-hood. ## Related links - https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/ - actions/checkout#959
## Description Support for Ubuntu 18 in Github Actions is deprecated and will be removed altogether in April 2023 - so this PR updates the CI workflow to us Ubuntu 22 - an LTS release with several more years of support at minimum. This change also updates the use of `actions/checkout` to `@v3` - which addresses a deprecation warning around an outdated Node version usage under-the-hood. ## Related links - https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/ - actions/checkout#959
Behaviour
Warning:
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/
Warning:
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/
As per https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Steps to reproduce this Issue
actions/checkout@v3
to checkout a repositoryThe text was updated successfully, but these errors were encountered: