Skip to content
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 for using set-output command #281

Open
namurphy opened this issue Apr 4, 2023 · 3 comments
Open

Deprecation warning for using set-output command #281

namurphy opened this issue Apr 4, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@namurphy
Copy link

namurphy commented Apr 4, 2023

What happened

I got the following warning message when using this action:

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/

The link is to this blog post, which describes how to fix it. The post says that the warning will turn into an error starting on 2023 June 1.

What you expected to happen

There should be no warning.

How to reproduce it

By setting this action up in a repository, after updating actions/checkout@v3.

The PR I found this warning message in is: PlasmaPy/PlasmaPy#2064

Thank you!

@namurphy namurphy added the bug Something isn't working label Apr 4, 2023
@namurphy
Copy link
Author

namurphy commented Apr 4, 2023

I didn't see a place where set-output gets used in this repo, so I'm wondering if it's in an upstream repo. 🤔

There were also some changes about the version of node.js changing, which is discussed in actions-ecosystem/action-add-labels#434

Another possibility is that one of the dependabot PRs might also fix this.

@namurphy
Copy link
Author

namurphy commented May 26, 2023

To follow up with some news on this, the lines in this blog post that said the commands would be deleted have been struck through. The commands still remain deprecated, though.

@nate-thirdwave
Copy link

I believe the solution is to bump the actions/core version to >=1.10 per the posting, as this repo does indeed use core.setOutput which backends into that call and is migrated to the new form automatically if my understanding is correct. #258 would address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants