-
Notifications
You must be signed in to change notification settings - Fork 62
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
fix: replacing deprecated set-output to use env instead #94
Conversation
Signed-off-by: Tobias Lindberg <[email protected]>
It would be super lovely if this PR was approved and merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @tobiasehlert and sorry for the very long delay getting back to this! Your change looks good to me, but it appears the whole repo needs some love. I'm gonna merge your PR as is and will fix the issues on another PR.
Thanks for the fix - would be good to tag a release, so downstream projects aren't at risk of failing on May31st. Thanks! |
@khos2ow is there any progress on the repo updates here? Looks like we've got about 2 weeks left and this will begin blocking pipelines |
Description of your changes
Replacing deprecated
set-output
to use env$GITHUB_OUTPUT
instead.Blogg post about deprecation:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
I have: