Skip to content

set-env and add-path are now disabled for security reasons #99

Description

@ggrossetie

Using the latest version published (v6), I get the following errors:

Error: Unable to process command '::set-env name=PYENV_ROOT::/opt/hostedtoolcache/pyenv_root/1.2.18/x64' 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: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
export PYENV_ROOT="/opt/hostedtoolcache/pyenv_root/1.2.18/x64"
Error: Unable to process command '::add-path::/opt/hostedtoolcache/pyenv_root/1.2.18/x64/bin' successfully.
Error: The `add-path` 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: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
Error: Unable to process command '::add-path::/opt/hostedtoolcache/pyenv_root/1.2.18/x64/shims' successfully.
Error: The `add-path` 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: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands

Is there a workaround, apart from setting ACTIONS_ALLOW_UNSECURE_COMMANDS?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions