You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When publishing an npm package, when the publishPath option is set, isCollaborator should detect package.json under publishPath instead of the current directory.
#1090
Closed
Ru1ers opened this issue
Mar 31, 2024
· 2 comments
When I execute publish npm in the root directory, he throws an exception
ERROR User xxxx is not a collaborator for release-it-test.
Documentation: https://git.io/release-it-npm
Apparently the error is telling me that I don't have publishing permissions for the project, which is no problem
But my project has a monorepo structure, and I cannot set the name in package.json in my root directory to the same name as the sub-package. This leads to the fact that what I release is a sub-project, and release-it detects the root directory.
When I execute publish npm in the root directory, he throws an exception
Apparently the error is telling me that I don't have publishing permissions for the project, which is no problem
But my project has a monorepo structure, and I cannot set the name in package.json in my root directory to the same name as the sub-package. This leads to the fact that what I release is a sub-project, and release-it detects the root directory.
This is the package.json of the subproject
This is package.json in the root directory
The text was updated successfully, but these errors were encountered: