ci: replace deprecated set-output commands with new syntaxes - #215
Open
MarlonPassos-git wants to merge 2 commits into
Open
ci: replace deprecated set-output commands with new syntaxes#215MarlonPassos-git wants to merge 2 commits into
MarlonPassos-git wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tip
The owner of this PR can publish a preview release by commenting
/publishin this PR. Afterwards, anyone can try it out by runningpnpm add radashi@pr<PR_NUMBER>.Summary
Recently, I have seen this warning error in CI.
So I opened this pull request, updates the GitHub Actions workflow to replace the deprecated set-output commands with the new recommended syntax.
Note
documentation https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Related issue, if any:
For any code change,
Does this PR introduce a breaking change?
No