We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug There is a warning during build: 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/
set-output
To Reproduce Steps to reproduce the behavior:
Expected behavior Remove warning
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
masesgroup#32: removed some warning for obsolete node version
0506e7d
#32: removed some warning for obsolete node version (#33)
0018f75
masesgroup#32: remove scheduled events because the action is executed…
3a4e575
… on every push
#32: remove scheduled events because the action is executed on every …
e4c78f8
…push (#35)
masesdevelopers
Successfully merging a pull request may close this issue.
Describe the bug
There is a warning during build:
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/To Reproduce
Steps to reproduce the behavior:
Expected behavior
Remove warning
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: