Skip to content
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

core.setOutput function will be disabled 1st June 2023 unless actions/core is updated. #12

Open
bmos opened this issue Oct 30, 2022 · 3 comments

Comments

@bmos
Copy link
Contributor

bmos commented Oct 30, 2022

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/

Now obviously you're not using stdout, but you are using the core.setOutput function:

core.setOutput('replaced', string.replace(regex, replaceWith));

Which according to the linked blog post, means you need to update actions/core to at least v1.10.0:

Action authors who are using the toolkit should update the @actions/core package to v1.10.0 or greater to get the updated saveState and setOutput functions.

It seems currently to be 1.4.0 as of this prior issue which discussed how to update it!

@bmos bmos changed the title The set-output command is deprecated and will be disabled soon. The set-output command is deprecated and will be disabled 1st June 2023. Oct 30, 2022
@bmos bmos changed the title The set-output command is deprecated and will be disabled 1st June 2023. core.setOutput function will be disabled 1st June 2023 unless actions/core is updated. Oct 30, 2022
@varxnnn
Copy link

varxnnn commented Dec 8, 2022

@bmos @frabert any updates on this? We can just update it from package-json imo.

@frabert
Copy link
Owner

frabert commented Dec 8, 2022

Sorry for the delayed response everybody. I published v2.4 which should fix this. If somebody can test this, I will close this issue.

@varxnnn
Copy link

varxnnn commented Dec 8, 2022

@frabert thank you! it works now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants