Deprecated set-env and add-path commands
See original GitHub issueGitHub is deprecating set-env
and add-path
commands, causing the GitVersion action to log the following warning when executed:
The
set-env
command is deprecated and will be disabled soon. 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/

I’m not sure what the fix is, because we are using v1.2.6
of @actions/core
already.
Action authors who are using the toolkit should update the
@actions/core
package tov1.2.6
or greater to get the updatedaddPath
andexportVariable
functions.
Issue Analytics
- State:
- Created 3 years ago
- Comments:44 (24 by maintainers)
Top Results From Across the Web
GitHub Actions: Deprecating set-env and add-path commands
Patching your actions and workflows 2.6 or greater to get the updated addPath and exportVariable functions. Action and workflow authors who are ...
Read more >'set-env' error when trying to build Android app using GitHub ...
I am new to GitHub Actions and want to build and deploy my Android app to "internal testing" at the Google Play store....
Read more >Github Actions set-env deprecation | [“Kirø~$”]
We get the following deprecation message in our github actions workflow. The `set-env` command is deprecated and will be disabled on November 16th....
Read more >allowed-unsecure-commands - Semgrep
... grants this workflow permissions to use the `set-env` and `add-path` commands. ... a different command than intended, resulting in arbitrary code execution....
Read more >Setting the PATH environment variable to include the ... - IBM
If you are using the Bourne, Korn, or BASH shell, use the following command: export PATH=$PATH:installation_path/vacpp/bg/12.1/bin/ · If you are using the C ......
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
I am not sure if it is something in our specific environment but we are actually getting the same error despite using v0.9.4 for both the setup and execute action.
We need to debug and see why it’s not working