-
Notifications
You must be signed in to change notification settings - Fork 23
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
The "set-output" command is deprecated and will be disabled soon
warning
#42
Comments
The
set-output command is deprecated and will be disabled soon
warniongThe
set-output command is deprecated and will be disabled soon
warning
The
set-output command is deprecated and will be disabled soon
warningThe"set-output" command is deprecated and will be disabled soon
warning
The"set-output" command is deprecated and will be disabled soon
warningThe "set-output" command is deprecated and will be disabled soon
warning
I checked this action and it seems like nowhere here set-output nor save-state are being used, so if you have any ideas why it might happen, I would be really thankful for any info! |
might be due to this |
Yeah, |
I'm using https://github.com/JasonEtco/actions-toolkit for this, which needs to bump its version of |
just checking in on this, did I understand you correctly that you'll fix it rather than asking Jason to update his? I didn't notice an issue for it over in his repo and I'm not sure it's being worked on anymore. Thanks! |
Yep! I'm slowly converting actions to |
😎 , appreciate it man! |
just curious, I presume this will still be released under v2, is that what you're thinking? |
I'm reasonably confident this will be a v2 update. If there are any changes which could be considered breaking (I don't intend to make any, but it all depends on the implementation) it'll go out as v3 |
I released this as v3 as v2 has code to handle the |
make sense, thanks! |
More info here
Every pull request on Osmosis finishes with this warning. Seems like this action is responsible for it. Ex: example
From the first link, my guess it is due to not using
@actions/core v1.10.0
but may be something elseThe text was updated successfully, but these errors were encountered: