-
Notifications
You must be signed in to change notification settings - Fork 252
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
Error: spawn npm ENOENT #193
Comments
Do you see more logs before the fatal? to maybe point to the right code line it crashed. |
Seeing the same problem with similar setup. No relevant logs before fatal crash
|
Can you try the latest version: https://github.com/phips28/gh-action-bump-version/releases/tag/v9.0.38 It has something to do with the workspace (but I am not using this actively in my own setups) |
Logging while using latest version (v9.0.38): I am using: On the job itself. Is that what you mean by workspace?
|
Are you running on a windows machine? |
Correct:
|
Ok then this action is not working on windows as it seems 😄 But you can make a PR to support windows:
|
Ah I see :P Can confirm this all works on ubuntu-latest indeed. Thanks for your assistance. |
I'm using this action to version bump after building the project and installing NPM packages.
However on the version bump action I get this error. I don't understand why, the runner is using node V 16.13.1.
My folder structure:
Root
---- ProjectA [folder]
------- dist [folder
------- readme.md
------- package.json
------- package-lock.json
---- ProjectB [folder
.gitignore
.readme
Action (partly):
The text was updated successfully, but these errors were encountered: