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

The set-env command is deprecated and will be disabled on November 16th #383

Open
JesperNJessen opened this issue Nov 11, 2020 · 7 comments

Comments

@JesperNJessen
Copy link

index.js uses set-env and add-path. Both will be disabled soon. As a result I'm seeing these warnings in my log:

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/
The `add-path` 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/
@yvescleuder
Copy link

I have the same problem.

@silv4b
Copy link

silv4b commented Nov 15, 2020

Me too :/

@peaceiris
Copy link

peaceiris commented Nov 15, 2020

@silv4b You mean this? https://github.com/silv4b/ti-icons-test/runs/1403737126?check_suite_focus=true#step:3:6
Your case is a problem of actions/setup-node, use the latest version v1.4.4 or v1.

@peaceiris
Copy link

peaceiris commented Nov 15, 2020

Actually, the actions/checkout does not use the core.addPath and core.exportVariable so I do not think this action throws the error message. Maybe, you need to check which action returns the message.

Duplicate of #361 and #380

@silv4b
Copy link

silv4b commented Nov 15, 2020

@silv4b You mean this? https://github.com/silv4b/ti-icons-test/runs/1403737126?check_suite_focus=true#step:3:6
Your case is a problem of actions/setup-node, use the latest version v1.4.4 or v1.

I was checking exactly that, it worked, thanks for your answer, this is my first contact with Actions.

@Jolg42
Copy link

Jolg42 commented Feb 4, 2021

Just got this today

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/ 

Seems that ACTIONS_ALLOW_UNSECURE_COMMANDS=true is a quick (unsecure) fix for it.

@victormanuelfrancodev
Copy link

not is recommended set insecure commands , try :
some like that
- run: echo "NOW=v$(date +'%Y%m%d.%H%M%S')" >> $GITHUB_ENV

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

6 participants