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

Set-output command is deprecated #601

Closed
ghost opened this issue Dec 10, 2022 · 5 comments
Closed

Set-output command is deprecated #601

ghost opened this issue Dec 10, 2022 · 5 comments
Labels
bug Something isn't working needs-triage This issue still needs to be triaged

Comments

@ghost
Copy link

ghost commented Dec 10, 2022

Describe the bug

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/

Expected Behavior

I am expecting echo "environment=development" >> $GITHUB_OUTPUT instead of echo "::set-output name=environment::development".

Current Behavior

Current behavior is using old set-output, for example echo "::set-output name=environment::development"

Reproduction Steps

Using aws-actions/configure-aws-credentials@v1 in our GitHub Actions script.

Possible Solution

Use "environment=development" >> $GITHUB_OUTPUT instead of echo "::set-output name=environment::development".

Additional Information/Context

No response

@ghost ghost added bug Something isn't working needs-triage This issue still needs to be triaged labels Dec 10, 2022
@ghost
Copy link
Author

ghost commented Dec 10, 2022

image

@levivannoort
Copy link

related issue on the dependency: actions/toolkit#1218

@bendrucker
Copy link

bendrucker commented Dec 21, 2022

I've left a comment in that issue, @actions/core has supported this and is backwards compatible as of ~2 months ago. I can work on a PR to fix this.

Hmm, seems that the dependency is up to date, investigating...

@bendrucker
Copy link

Turns out this is fixed in main and just not released.

#521

Switching to @v1-node16 resolves it and should generally be the default for most users until v2.

@ghost ghost closed this as completed Dec 25, 2022
@github-actions
Copy link

⚠️Comment Visibility Warning⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage This issue still needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants