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
Hi @NullDivision, by design semver is tag-based, which means it uses tags to define the current version so it doesn't make sense to add an option to skip tagging, it would break version calculation. Note that there's already an open PR about that (#687) but I would not merge it until we choose to support other strategies to get the current version. For now, it's not a priority.
+1 for this. It would be nice to at least support that option for more advanced cases.
The problem with creating tags after versioning each given individual package, is that they are blocking the git process.
In my use case, the difference between versioning in a single NX process and in 5 parallel processes is quite dramatic, as I use semver to version an nx monorepo with around 200 independent packages. I'm pushing (and squashing) manually after the main process finishes.
And right now the tags are the only reason why I cannot scale up the parallel tasks.
It would be nice to be able to skip creating tags for specific projects.
The use case I would currently like is to skip creating tags for packages in our /libs directory while still creating them for /apps.
The text was updated successfully, but these errors were encountered: