semantic-release-action: Command failed: npm install semantic-release
Describe the bug Today i run it and had this error:
Run cycjimmy/semantic-release-action@v2
added 2 packages, and audited 3 packages in 963ms
found 0 vulnerabilities
Error: Error: Command failed: npm install @semantic-release/changelog @semantic-release/git @semantic-release/exec --silent
Workflow No change on the worklow file, was passing 3 days ago.
Expected behavior Not fail like in the last months
Additional context Download action repository ‘actions/checkout@v2’ (SHA:5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f) Download action repository ‘cycjimmy/semantic-release-action@v2’ (SHA:116647291d9b7bef1f5a4315deedd3f46ed4218b)
How i can debug this?
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 7
- Comments: 17 (3 by maintainers)
Commits related to this issue
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/addonfactory-ucc-library by deleted user 3 years ago
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/addonfactory-ucc-generator by deleted user 3 years ago
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/pytest-splunk-addon by deleted user 3 years ago
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/pytest-splunk-addon by deleted user 3 years ago
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/addonfactory-ucc-library by deleted user 3 years ago
- ci: fix release step More details here: https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to splunk/addonfactory-ucc-generator by deleted user 3 years ago
- chore: fix release action Something about semantic-release version? https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to supabase/storage by soedirgo 2 years ago
- chore: fix release action Something about semantic-release version? https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to supabase/storage by soedirgo 2 years ago
- Chore: Update semantic-release to solve error installing. https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to rigetti/qcs-sdk-rust by dbanty 2 years ago
- fix(nodejs-server-release): Specify semantic-release plugin versions explicitly To try to work around https://github.com/cycjimmy/semantic-release-action/issues/79 — committed to relaycorp/shared-workflows by gnarea 2 years ago
- Fixes semantic release breakage see https://github.com/cycjimmy/semantic-release-action/issues/79#issuecomment-955463633 — committed to googlemaps/js-samples by amuramoto a year ago
- chore: more fix for semantic release action per https://github.com/cycjimmy/semantic-release-action/issues/79#issuecomment-955463633 — committed to googlemaps/google-maps-ios-utils by wangela a year ago
- chore: fix workflows (#440) * chore: allow dependabot to call test workflow * chore: more fix for semantic release action per https://github.com/cycjimmy/semantic-release-action/issues/79#issuecom... — committed to googlemaps/google-maps-ios-utils by wangela a year ago
@pegiadise I don’t think it’s the reason.
This worked for me:
i believe its the git plugin that is causing the issue. The latest version (10.0.0) has a dependency on semantic-release@18.0.0 so it you havent fixed the plugin version then it could be throwing an error with this by trying to grab the latest version, yet all other plugins havent been updated to support (they were reporting support <= 18.0.0). I set the @semantic-release/git@9.0.1 to resolve things and work around the conflict here.
looks like you need to add
to your action
Got the same error
Fixed by specifying a
setup-nodestep and it works nowYeah that’s how I found it. I’m not sure why
--silentis added by default but this should definitely be documented.