deperecated dependency: 100% failure
See original GitHub issueDo the checklist before filing an issue:
- Is this related to the
actions-rs
Actions? If you think it’s a problem related to Github Actions in general, use GitHub Community forum instead: https://github.community - You’ve read the Contributing section about bugs reporting: https://github.com/actions-rs/.github/blob/master/CONTRIBUTING.md#reporting-bugs
- Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
Description
A clear and concise description of what the bug is.
See https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
and https://github.com/actions-rs/toolchain/pull/114 for a PR that fixes the issue
Workflow code
Paste that part of your workflow yaml file that causes the bug in here.
Alternatively you can remove that code block and insert direct link to your workflow file.
Ensure that link points to the specific commit, and not just to the master branch.
Action output
/usr/bin/docker exec d25f5c30aa8e784012badcab5bc6344c4bce5a4c72f595ca756380dfab46bd95 sh -c "cat /etc/*release | grep ^ID"
/__w/_temp/42a68bee-6546-42ed-9628-d75de2498306 --default-toolchain none -y
info: downloading installer
error: $HOME differs from euid-obtained home directory: you may be using sudo
error: $HOME directory: /github/home
error: euid-obtained home directory: /root
info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
info: skipping toolchain installation
Rust is installed now. Great!
To get started you need Cargo's bin directory ($HOME/.cargo/bin) in your PATH
environment variable. Next time you log in this will be done
automatically.
To configure your current shell run source $HOME/.cargo/env
Error: Unable to process command '::add-path::/github/home/.cargo/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/
Expected behavior
The $PATH
to be properly set
Additional context
This will causes a lot of breakages out there I guess 😛
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
peerDependency problem causes ember new to fail on npm 8 ...
It looks like npm can be persnickety about 4.4.0-beta.1 not meeting the requirement ^3.2.0 || ^4.0.0 because the tag throws things off.
Read more >NPM install fails, OSX - node gyp - Stack Overflow
I could get my project from github just fine but whenever I run npm install to fetch the dependencies I encounter this gyp...
Read more >find-deprecated - npm Package Health Analysis - Snyk
A node package for finding deprecated project dependencies. Visit Snyk Advisor to see a full health score report for find-deprecated, including ...
Read more >Installing anypoint-cli with NPM shows 'WARN' and ...
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN ...
Read more >[Docker Course 4-13] Issue on npm install step
I've facing an issue while installing the app dependencies, returning an user permission denied while accessing the /app directory. Can you guys ...
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 FreeTop 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
Top GitHub Comments
@svartalf thanks a lot for the quick fix, can confirm it works fine now 👍
Thank you for notification, @bilelmoussaoui! Fix was added and released as a new
@v1
version; I apologize for not handling this deprecation issue earlier.Can anyone in this thread additionally confirm that it works for them now?