-
-
Notifications
You must be signed in to change notification settings - Fork 472
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
Update the set-output command (deprecation warning) #265
Comments
After cleaning up some workflows for this very reason, this is the last one I needed to update, and I like using this action with the gitchangelog-action. So I tested both upgrade PRs on top of current master, and that (mostly) takes care of the (end-user) workflow deprecation warnings (yay!) however it still has a similar list of npm package deprecation/unmaintained/vulnerability warnings in the test log. Sadly I'm already out of time/bandwidth... |
One could consider abandoning this action and using GitHub CLI instead. GitHub CLI is preinstalled on all GitHub-hosted runners. |
@jo-tools Can you run the GitHub CLI from GitHub Actions? Would you have an example? |
@Vadorequest yes, click @jo-tools’ first link. |
Thanks, I've eventually migrated to using GH CLI as well. Here is an example: |
What would you like to be added?
When using this Action in a Workflow, GitHub displays a warning:
The 'set-output' command is deprecated and will be disabled soon.
So the
set-output
command should be updated... so that no warnings of deprecations are being displayed.Why is this needed?
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/The text was updated successfully, but these errors were encountered: