Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

build now failing due to github blocking set-env

See original GitHub issue

Hi,

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 GitHub Comments

1reaction

DeLaGuardocommented, Nov 16, 2020

Hi, this issue has already being fixed in master. Please use DeLaGuardo/setup-clojure@master this string in your actions to get latest code.

1reaction

filipesilvacommented, Nov 16, 2020

Meanwhile you can set the env variable as described in the error message:

      - uses: DeLaGuardo/setup-clojure@2.0
        env:
          ACTIONS_ALLOW_UNSECURE_COMMANDS: true
        with:
          tools-deps: '1.10.1.536'