The set-output command is deprecated and will be disabled soon
#219
Comments
|
I'm glad you are a happy user of this action :) |
jeremyckahn
added a commit
to jeremyckahn/farmhand
that referenced
this issue
Dec 29, 2022
jeremyckahn
added a commit
to jeremyckahn/farmhand
that referenced
this issue
Dec 30, 2022
* chore: use node 18 - Required upgrade to node-sass 8.0.0 - Required --openssl-legacy-provider - See: https://nodejs.org/en/blog/release/v17.0.0/#openssl-3-0 - See: https://stackoverflow.com/a/69699772 - See: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ * fix: use --openssl-legacy-provider for build * fix: update to non-deprecated MUI APIs - See: actions/upload-artifact#351 - See: dorny/test-reporter#219 * chore: unpin GitHub action versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Team,
We are using this Github action and this is really awesome. Would like to get one thing to your notice is that GitHub is migrating the set output to a different method. So was wondering if this is already in process or when can we expect the update on the action.
Below is the error message and screenshot for your reference
Theset-outputcommand 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: