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 warnings due to set-output #11
Comments
Yeah, I've been meaning to fix this. Thanks for the issue! |
@hynek FYI the actual docs section describing this is https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter. Not sure why they didn't link it directly... |
Using the `::set-output` has been suddenly deprecated the other day, without a clear deadline [1]. The new way of achieving the same is to append key-value pairs to the environment file that can be located by looking up the path recorded in the `$GITHUB_OUTPUT` environment variable [2]. This patch implements this new mechanism. The change is not a user-facing update and the behavior should remain the same. Resolves re-actors#11. [1]: https://hynek.me/til/set-output-deprecation-github-actions/ [2]: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter
@hynek they've later updated the blog post to include the examples: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/#examples. |
yeah they reached out to me |
GitHub has deprecated the set-output way, so I'm getting warnings in my workflows from alls-green.
Since they provided zero guidance how to fix it, I've written it down myself: https://hynek.me/til/set-output-deprecation-github-actions/
tldr:
echo "::set-output name=KEY::VALUE"
→echo "KEY=VALUE" >>$GITHUB_OUTPUT
The text was updated successfully, but these errors were encountered: