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
You can just add "private": true to the package.json
Is it a core use case or an opt-in use case that semantic-release be able to publish to npm?
we do plan to decompose the semantic-release module and create @semantic-release/core, exactly for use cases like this where you are not interested in npm.
Is it a core use case or an opt-in use case that semantic-release be able to publish to npm?
If not, I think it would increase the value of the setup tool to be able to produce configurations where npm publishing is only optional
The text was updated successfully, but these errors were encountered: