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 #109

Closed
Nimesha-Premaraja opened this issue Oct 26, 2023 · 5 comments
Closed

The set-output command is deprecated #109

Nimesha-Premaraja opened this issue Oct 26, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@Nimesha-Premaraja
Copy link

Describe the bug

The set-output command is deprecated for GitHub Actions. We get following warning when run the GitHub Action

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/

How can we reproduce it?

should be updated to write to the new GITHUB_STATE and GITHUB_OUTPUT environment files as mentioned in this documentation
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Environment information

runs-on : ubuntu-latest
uses: terraform-docs/[email protected]

@Nimesha-Premaraja Nimesha-Premaraja added the bug Something isn't working label Oct 26, 2023
@codymaust
Copy link

codymaust commented Nov 14, 2023

#97 and #101 are for the same issue

(edit: removed info that was incorrect)

@atrull
Copy link

atrull commented Nov 18, 2023

+1

1 similar comment
@actuarysailor
Copy link

+1

actuarysailor added a commit to actuarysailor/gh-actions that referenced this issue Dec 22, 2023
### Description of your changes
Trying to get rid of the deprecated `set-output` issue.

fixes terraform-docs#109

I have:

- [x] Read and followed terraform-docs' [contribution process].

### How has this code been tested
I ended up changing some of the workflow files to do something different outside of your account but still using the same code inside of your account.  This allowed me to better test/run your validation steps externally.

[contribution process]: https://git.io/Jt3K5
actuarysailor added a commit to actuarysailor/gh-actions that referenced this issue Dec 22, 2023
### Description of your changes
Trying to get rid of the deprecated `set-output` issue.

fixes terraform-docs#109

I have:

- [x] Read and followed terraform-docs' [contribution process].

### How has this code been tested
I ended up changing some of the workflow files to do something different outside of your account but still using the same code inside of your account.  This allowed me to better test/run your validation steps externally.

Signed-off-by: actuarysailor <[email protected]>
actuarysailor added a commit to actuarysailor/gh-actions that referenced this issue Dec 22, 2023
### Description of your changes
Trying to get rid of the deprecated `set-output` issue.

fixes terraform-docs#109

I have:

- [x] Read and followed terraform-docs' [contribution process].

### How has this code been tested
I ended up changing some of the workflow files to do something different outside of your account but still using the same code inside of your account.  This allowed me to better test/run your validation steps externally.

Signed-off-by: shiro Name <[email protected]>
actuarysailor added a commit to actuarysailor/gh-actions that referenced this issue Dec 22, 2023
### Description of your changes
Trying to get rid of the deprecated `set-output` issue.

fixes terraform-docs#109

I have:

- [x] Read and followed terraform-docs' [contribution process].

### How has this code been tested
I ended up changing some of the workflow files to do something different outside of your account but still using the same code inside of your account.  This allowed me to better test/run your validation steps externally.

Signed-off-by: shiro <[email protected]>
@ViacheslavKudinov
Copy link

Could be good to get this "concern" fixed.

@khos2ow
Copy link
Member

khos2ow commented Mar 23, 2024

Closing this in favor of its duplicate of #97 which is fixed in #94.

@khos2ow khos2ow closed this as completed Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment