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

command is deprecated and will be disabled soon #276

Closed
5 tasks done
godcong opened this issue Oct 14, 2022 · 6 comments
Closed
5 tasks done

command is deprecated and will be disabled soon #276

godcong opened this issue Oct 14, 2022 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@godcong
Copy link

godcong commented Oct 14, 2022

Description:
A clear and concise description of what the bug is.

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/

Action version:
Specify the action version

actions/setup-go@v3

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:

1.19.2

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
see my actions:
https://github.com/babyname/fate/actions/workflows/go.yml

Expected behavior:
A description of what you expected to happen.
use new
Actual behavior:
A description of what is actually happening.
the env setting need update

PS: setup-go seems that GOROOT is not set. when i use $GOROOT/bin/go will failed

@godcong godcong added bug Something isn't working needs triage labels Oct 14, 2022
@Xunzhuo
Copy link

Xunzhuo commented Oct 14, 2022

+1, this needs some updates.

@marko-zivic-93
Copy link
Contributor

Hello @godcong
Thank you for your issue. We will investigate it and come back to you as soon as possible with some news :)

@reubenmiller
Copy link

The deprecation warning should be removed once the @actions/core npm package is updated to v1.10.0 or later (see github announcement).

The main branch is already using this version, so it probably not much to do apart from cutting a new release.

@e-korolevskii
Copy link
Contributor

Hi @godcong!

Yesterday we released a new version that includes a solution to this issue.
Could you confirm that it is now working as expected?

@e-korolevskii e-korolevskii self-assigned this Oct 19, 2022
@reubenmiller
Copy link

reubenmiller commented Oct 19, 2022

Confirmed (at least for my project). I just checked the logs and the above warning is now gone when using setup-go. I removed the link to this issue. Thanks for the fast response!

@dmitry-shibanov
Copy link
Contributor

Thank you for your response @reubenmiller. I'm going to close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants