-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
set-output is going to be deprecated in 2023 #10
Comments
Great to hear you like the action. If you would be able to PR the modification, I'd really appreciate it! Thanks! |
UP |
issue: #10 changed set-output to GITHUB_OUTPUT
The fix has been released, thanks @jospapePAQT ! |
No warnings anymore, but I have empty value while trying to access coverage and other values
|
it is now stored in
|
The README is not up to date anymore. |
It doesn't work for me as well :(
But in action logs I see output with
|
@pfy-oleksii-storozhylov @greatislander @jospapePAQT Apologies for the late response. Due to personal reasons I was unable to work on this sooner. I have now pushed the fixes to the action in #13. The README on how to use the output remains correct. It was simply a faulty implementation of setting the output in #11 So any new runs of the workflow should show proper output again, as you can see here: |
First of all, thanks for the great workflow! I got a deprecation warning when using it related to this: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
I think the change in
helpers/Output
would be fairly minimal and I'd be happy to file a PR if you would be open to that. Thanks in advance.The text was updated successfully, but these errors were encountered: