-
Notifications
You must be signed in to change notification settings - Fork 116
Issues: semantic-release/npm
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
align approach for concatenating
.npmrc
files to better align with default npm behavior
#791
opened May 3, 2024 by
travi
Failed step "prepare" of plugin "@semantic-release/npm" due to reading malformed path
#773
opened Apr 7, 2024 by
joshunrau
Support for custom package.json properties to write changelist entries
#761
opened Mar 5, 2024 by
ggrafhalfbrick
Command failed with exit code 1: npm version 0.22.2 --userconfig
#651
opened Jul 31, 2023 by
CalicoNino
Provide a better error message in case of an E400 bad request without further explanation from npm
#519
opened Sep 23, 2022 by
gr2m
npm publish fails /
npm publish <folder>
publishes from cwd folder
#504
opened Jul 31, 2022 by
unlight
Upgrade peer dependency semantic-release to version 19.0.3 or later to fix known vulnerability
#498
opened Jul 1, 2022 by
ocofaigh
Clarification on the proper way to change settings when doing a fork
#483
opened May 13, 2022 by
sneko
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.