Skip to content
New issue

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

Error: The set-env command is disabled. #19

Open
G1K opened this issue Mar 26, 2021 · 1 comment
Open

Error: The set-env command is disabled. #19

G1K opened this issue Mar 26, 2021 · 1 comment

Comments

@G1K
Copy link
Contributor

G1K commented Mar 26, 2021

Unable to process command '::set-env name=HOST_TMP_DIR::/tmp/builder' 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/

If you replace it with what they recommend, then setting variables from the docker container does not pass.
https://github.com/G1K/openwrt-fastbuild-actions/runs/2205313841?check_suite_focus=true
@tete1030 Please see how I tried to fix it. Can you suggest a way out of this situation?

@G1K
Copy link
Contributor Author

G1K commented Mar 26, 2021

So far I decided to turn on ACTIONS_ALLOW_UNSECURE_COMMANDS

But it seems to me that soon such commands will be banned altogether. After deprected

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

No branches or pull requests

1 participant