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

The set-output command is deprecated and will be disabled soon. #180

Closed
5 of 10 tasks
justin-newman opened this issue Feb 6, 2023 · 5 comments
Closed
5 of 10 tasks
Labels
question Further information is requested

Comments

@justin-newman
Copy link

Description

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/

This is just a warning really for now, but soon enough it will cause the action to fail. I'm sure the update can be lumped in with pretty much any other update that needs to happen.

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • example code related
  • testing related
  • discussion

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version:
All
node version:
N/A
OS version(s):
N/A

Steps to reproduce:

  1. Run the action successfully

Expected result:

The warning should not be there.

Actual result:

The warning was there.

Attachments:

Logs, screenshots, screencast, sample project, funny gif, etc.

@seratch seratch added the question Further information is requested label Feb 7, 2023
@seratch
Copy link
Member

seratch commented Feb 7, 2023

Hi @justin-newman, thanks for writing in!

Our understanding is that upgrading @actions/core to 1.10+ should resolve this issue. Refer to #142 (comment) for more details.

@justin-newman
Copy link
Author

Ok that's great. As long as it is in the works, I didn't see any issues for it yet so I thought I would make sure.

@bombillazo
Copy link

How does one "upgrade @actions/core"? I'm using the slack-github-action so not sure how one upgrade this

@justin-newman
Copy link
Author

How does one "upgrade @actions/core"? I'm using the slack-github-action so not sure how one upgrade this

We don't do anything, it looks like the necessary changes have already been made in the repo, we just need to wait for the next version of the action to be released and then it will be upgraded.

@hodigabi
Copy link

hodigabi commented Apr 6, 2023

The latest version resolves this warning, doesn't it?

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

No branches or pull requests

4 participants