Open
Description
Describe the enhancement
In workflow, set-output
command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information, see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Activity
set-output
perl-actions/install-with-cpm#15core.setOutput
? #1218paolorevillosa commentedon Feb 22, 2023
Does anyone find a fix for this?
jongwooo commentedon Feb 22, 2023
@paolorevillosa See actions/toolkit#1337
jongwooo commentedon Feb 22, 2023
@paolorevillosa Oh I just saw your comment #1218 , what I mentioned above was for workflow and I didn't find a solution for
core.setOutput
inactions/core
. If I find a solution, I'll share it with you.twohlix commentedon May 11, 2023
@ksaunders the code I'm reading only does it one of the ways. But it keeps running it the old way for one of my actions. Code I'm seeing 1.10.0:
so if
process.env['GITHUB_OUTPUT']
is empty it does it the old way withissueCommand('set-output'])
, but if its not empty it does it the new way.One of my actions must be evaluating
process.env['GITHUB_OUTPUT']
to empty as I'm using actions/core 1.10.0 and still getting theset-output
warning.Seems frustrating that the library which we're supposed to use will sometimes try it in a deprecated way. I'm also pretty bad at debugging github actions so I'm drawing a blank why my action would evaluate the GITHUB_OUTPUT as not there?
rentziass commentedon May 19, 2023
Hey @twohlix 👋 you're correct in that old behaviour is still present in
actions/core
for backwards compatibility reasons. Runner should be settingGITHUB_OUTPUT
in your jobs, would you able to please validate the env variable is there and is not being unset/overwritten? You should only get a warning if one of this is true:actions/core
< 1.10.0GITHUB_OUTPUT
is not setecho "::set-output name={name}::{value}"
)Does your action have any other dependencies that could affect this? Also if your action is public I'd be happy to have a look :)
8 remaining items