Publishing docs to GitHub pages fails because set-env has been deprecated #288
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
The
Publishing docs to GitHub pages
GitHub action has been failing for a couple months with this error message:The
set-env
command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting theACTIONS_ALLOW_UNSECURE_COMMANDS
environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/What is the new behavior?
Set the
CURRENT_BRANCH
andLATEST_DOCS_BRANCH
environment variables without usingset-env
as recommended by GitHub.Does this introduce a breaking change?
Other information
I was able to test by pushing the changes to my VSDK fork and creating a branch from that fork.
Clean test run here: https://github.com/jeffngo/virtualization-sdk/actions/runs/424167649