build now failing due to github blocking set-env
See original GitHub issueHi,
From today, November 16 2020, github has blocked all set-env
commands from working, i.e.,
The `set-env` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
This is now causing the action to fail to build projects:
Unable to process command '::set-env name=CLOJURE_INSTALL_DIR,::/opt/hostedtoolcache/ClojureToolsDeps/1.10.1-708/x64/lib/clojure' successfully.
and
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/
and
Run DeLaGuardo/setup-clojure@2.0
/bin/tar xz -C /home/runner/work/_temp/temp_898646021 -f /home/runner/work/_temp/c1015bd7-c452-4207-b9fd-c514fc8975d0
Error: Unable to process command '::set-env name=CLOJURE_INSTALL_DIR,::/opt/hostedtoolcache/ClojureToolsDeps/1.10.1-708/x64/lib/clojure' 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/
Error: Unable to process command '::add-path::/opt/hostedtoolcache/ClojureToolsDeps/1.10.1-708/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: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Is there a remediation for this?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Environment variables are not applied on container build #1837
I've spent today about 5 hours trying to figure this out. I've tried basically to use vars.env file to take username from it...
Read more >testing: add TB.Setenv() · Issue #41260 · golang/go - GitHub
As a result, tests either fail when they shouldn't or worse: don't fail when they should. In the first scenario (failing test), debugging...
Read more >"Error in Sys.setenv(PATH = new_path) : wrong length for ...
Now when I try to connect I get the error message: "Error in Sys.setenv(PATH = new_path) : wrong length for argument" > library(reticulate) ......
Read more >Semantic release blocked by always-failing Travis CI ... - GitHub
We have semantic-release setup but it never triggers because the Travis CI always fails on push. I think the sequence is: PR is...
Read more >Windows Server: Error: failed to retrieve package #326 - GitHub
To me it seems that the execution of renv:::renv_available_packages in the second block does not even try to get the renv_available_packages, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi, this issue has already being fixed in master. Please use
DeLaGuardo/setup-clojure@master
this string in your actions to get latest code.Meanwhile you can set the env variable as described in the error message: