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
So after some research it appears the majority of repos use v prefixes and tooling actually works better with the prefixes. I'm thinking of doing one more breaking change which includes:
removing --prefix and adding --unprefixed.
make the tag include a v by default, while excluding it in the tag message.
This would match npm behaviour with the default options and is probably the best way forward.
The text was updated successfully, but these errors were encountered:
Actually, I decided against this. It'd be kind of bad for users having to adopt to another breaking change, and I still prefer 'v'-less tags on my own projects because those are actual semvers.
So after some research it appears the majority of repos use
v
prefixes and tooling actually works better with the prefixes. I'm thinking of doing one more breaking change which includes:--prefix
and adding--unprefixed
.v
by default, while excluding it in the tag message.This would match npm behaviour with the default options and is probably the best way forward.
The text was updated successfully, but these errors were encountered: