-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
command deprecation
#75
Comments
Should be fixed by v2.2.1 |
Hello @mindsers, I'm still seeing these warnings with Any clues? |
(Aside: The README claims |
Agree, I'm seeing the same issue. For some reasons compiled version of the action has not changed: function setOutput(name, value) {
process.stdout.write(os.EOL);
command_1.issueCommand('set-output', { name }, value);
} This is how it should look like: function setOutput(name, value) {
const filePath = process.env['GITHUB_OUTPUT'] || '';
if (filePath) {
return file_command_1.issueFileCommand('OUTPUT', file_command_1.prepareKeyValueMessage(name, value));
}
process.stdout.write(os.EOL);
command_1.issueCommand('set-output', { name }, utils_1.toCommandValue(value));
} |
Looking. Weird that the built version didn't change. I'll publish a new version with the fix soon. |
Hi!
Thanks for the useful action. Unfortunately lately we started getting this warning:
Could you please update your
@actions/core
dependency to at least version1.10.0
.Thank you!
The text was updated successfully, but these errors were encountered: