-
Notifications
You must be signed in to change notification settings - Fork 74
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
Action modifies user's npmrc #15
Comments
For security reasons, this GitHub Action does not write your NPM auth token to the However, the bug that you've discovered is that this action leaves that placeholder in your Ultimately, this is a bug 🐛 in this GitHub Action. It should restore the Workarounds
-- OR --
|
I am also getting the same problem when writing any command related to npm. So I solved by node or nodemon. so when you want to start your server use the node and when you want to install any package just remove this and then install it will work.
|
I am also getting this problem but I find a solution when I am pushing my repo on Heroku so I notice that Heroku run the command react-script start or build
|
as @JamesMessinger say this definitely a bug 🐛 was able to fix this by setting up the
|
you can also replace the |
This would be great it if it was documented, I was bashing my head as to why Related fix https://github.com/matrix-org/matrix-js-sdk/pull/2717/files |
Rough plan for this bug:
This is the same exact strategy used by |
- Upgrade JS-DevTools/npm-publish to v2.1.0 - Remove workaround for bug JS-DevTools/npm-publish#15
- Upgrade JS-DevTools/npm-publish to v2.1.0 - Remove workaround for bug JS-DevTools/npm-publish#15 - Remove usage of `jq` in favor of npm-publish output
- Upgrade JS-DevTools/npm-publish to v2.2.0 - Remove workaround for bug JS-DevTools/npm-publish#15 - Remove usage of `jq` in favor of npm-publish output
- Upgrade JS-DevTools/npm-publish to v2.2.0 - Remove workaround for bug JS-DevTools/npm-publish#15 - Remove usage of `jq` in favor of npm-publish output Signed-off-by: Michael Cousins <michael@cousins.io>
- Upgrade JS-DevTools/npm-publish to v2.2.0 - Remove workaround for bug JS-DevTools/npm-publish#15 - Remove usage of `jq` in favor of npm-publish output Signed-off-by: Michael Cousins <michael@cousins.io>
I get the following error when using this action as github workflow using self hosted runner. It doesn't fail the build and it happens to all npm commands in the job.
Here's my workflow file:
Edit:
After playing around a bit, I was able to do a workaround by setting
INPUT_TOKEN
to empty string.The text was updated successfully, but these errors were encountered: