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
It looks like this plugin somehow causes release-it to require npm login, even if the npm publish step is disabled. My release-it.json looks like the following:
Apologies, I see now that the skipChecks option provides me the ability to avoid this 💯
However, it seems to me like this should be the default, as release-it by default doesn't require you to be authenticated if NPM publishing is disabled.
We encountered this issue too having adopted release-it-yarn-workspaces in addition to a release-it config we've been running for ~6 months now. It's particularly tricky as it only presented itself in CI, whereas running locally did not encounter this issue, we weren't expecting this failure as we'd set NPM publish to false at both levels:
It looks like this plugin somehow causes release-it to require
npm login
, even if thenpm publish
step is disabled. Myrelease-it.json
looks like the following:And my root
package.json
includes the two packages I have under a subdirectory:When I run
release-it
with this configuration, it asks me to authenticate, even though I'm not publishing to NPM.The text was updated successfully, but these errors were encountered: