Skip to content

[BUG] CI breaks when trying to set env var, updating how env vars are set - #318

Merged
czgu merged 2 commits into
masterfrom
kartik/fix_ci_breaking_set_env
Nov 17, 2020
Merged

czgu merged 2 commits into
masterfrom
kartik/fix_ci_breaking_set_env

Conversation

@darapuk

@darapuk darapuk commented Nov 17, 2020

Copy link
Copy Markdown
Contributor
Run echo "::set-env name=PY::$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')"
Error: Unable to process command '::set-env name=PY::c19639f9a84382269728f4ed835489e2160195648d7a2fcffd6a3bf36146c743' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_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/

@darapuk
darapuk requested a review from czgu November 17, 2020 00:14
@czgu

czgu commented Nov 17, 2020

Copy link
Copy Markdown
Collaborator

Thank you!

@czgu
czgu merged commit eb3c1dc into master Nov 17, 2020
@czgu
czgu deleted the kartik/fix_ci_breaking_set_env branch November 17, 2020 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants