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.

Sign up for GitHub

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

Jump to bottom

Deprecated set-output command is in use in versions.yml #606

Closed
2 of 5 tasks
willalder opened this issue Oct 24, 2022 · 3 comments
Closed
2 of 5 tasks

Deprecated set-output command is in use in versions.yml #606

willalder opened this issue Oct 24, 2022 · 3 comments
Assignees
@dmitry-shibanov
Labels
bug Something isn't working

Comments

@willalder
Copy link

Description:
The set-output command has been deprecated, but is still in use on lines 181 and 192 of versions.yml

Action version:
v3

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
Node v14, Yarn v1.22.19

Repro steps:
Run a job that uses setup-node@v3, select your action run, and check the summary.

Expected behavior:
A good, clean run with no warnings or errors.

Actual behavior:
The annotations for the job run include warnings that the set-output command has been deprecated, and will be disabled soon.

set_output_warning
@willalder willalder added bug Something isn't working needs triage labels Oct 24, 2022
willalder added a commit to torusco/github-workflows that referenced this issue Oct 24, 2022
@willalder
Added comment to yarn-test.yaml
3324e20 
Added comment explaining why setup-node@v3 action causes warnings about deprecated set-output command.  Included a link to a bug I filed requested that this be changed: actions/setup-node#606
@dmitry-shibanov dmitry-shibanov mentioned this issue Oct 25, 2022
Merged
2 tasks
@dmitry-shibanov
Copy link
Contributor

Hello @willalder. Thank you for your report. We created the pull request to get rid of this warnings.

@dmitry-shibanov dmitry-shibanov self-assigned this Oct 25, 2022
@willalder
Copy link
Author

Thanks @dmitry-shibanov! I'll watch for the fix. Much appreciated.

@dmitry-shibanov
Copy link
Contributor

Hello @willalder. We've merged it should work as expected. For now I'm going to close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmitry-shibanov dmitry-shibanov

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dmitry-shibanov @willalder