Github actions will be deprecating the use of ::set-output and moving to Environment Variables

[christian-ci]

When the action runs we get this warning:

Warning: The `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/

Other than that that's it. Thanks

[jbutcher5]

Alright thank you for letting me know, I will get round to sorting this soon.

[christian-ci]

No prob. Thanks to you as well!

[jbutcher5]

I have tried fixing this following the information on the github blog post but to no success, this should just have gone away by updating @actions/core to 1.10.0 but currently no success (i.e. we shouldn't have this issue to begin with). I am just going to come back to this possibly in a month or two, see if https://github.com/actions/toolkit/issues sorts itself out.

[christian-ci]

Sure thing. As far as I can tell aws-actions devs did the same with @actions/core. Thanks for checking it out.

[christian-ci]

I just remembered that FYI: save-state is also deprecating. aws-actions/ecr-login is a reference that has the same issue w/ the save-state. Maybe that helps out.

[kennyheard]

@jbutcher5 Did you have any luck resolving this issue?

[jbutcher5]

@kennyheard honestly I have lost all interest in maintaining this repository. If there was a pr made for it I would happily look over it and merge it but otherwise I am just going to work on other things and not update this repo.

[deejgregor]

The only use of set-output that I see in this repo is in

read-yaml/dist/index.js

Line 365 in d1d6dd0

command_1.issueCommand('set-output', { name }, value);

-- it looks like this is a generated file and was last updated in 2021. Does it need to be regenerated?