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
Thanks for the v2.1.1 release @caarlos0, that solved the Windows issue!
However there's still a behavior change in this version that's worth mentioning. I have a monorepo where all components are versioned in unison. Starting in v2.1 I can no longer get the current tagged version in scripts and Makefiles within sub-directories. Unless I explicitly specify the pattern and prefix arguments, #161 means svu will always assume I'm in a sub-package now.
I'm not sure what the best solution for this is, but IMO the new behavior feels overly opinionated/unexpected.
The text was updated successfully, but these errors were encountered:
I'm not sure what the best solution for this is, but IMO the new behavior feels overly opinionated/unexpected.
@NathanBaulch, I agree. This feels like a change that should be rolled back. While it is a new feature, it broke existing functionality and I don't think both can exist without some extra flag/configuration to say "be more opinionated".
Thanks for the v2.1.1 release @caarlos0, that solved the Windows issue!
However there's still a behavior change in this version that's worth mentioning. I have a monorepo where all components are versioned in unison. Starting in v2.1 I can no longer get the current tagged version in scripts and Makefiles within sub-directories. Unless I explicitly specify the pattern and prefix arguments, #161 means
svu
will always assume I'm in a sub-package now.I'm not sure what the best solution for this is, but IMO the new behavior feels overly opinionated/unexpected.
The text was updated successfully, but these errors were encountered: