turbo-version
Automatically versioning for monorepos
OTHER License
Bot releases are hidden (Show)
Fix branchName strategy - change to use date to define last merge and define new tag version.
Published by jucian0 12 months ago
Branch name strategy
TurboVersion uses the Git branch name to determine the next version, by default TurboVersion will use [major, minor, patch] as the branch name pattern, for example, if your current version is 1.2.3, and you have a branch named patch, the next version will be 1.2.4 when the patch branch is merged into the main branch.
🚀
Published by jucian0 over 1 year ago
🚀 Initial Release of Turbo Version
We're excited to announce the initial release of Turbo Version, a solution for versioning and releasing packages in monorepos! 🎉
Turbo Version is a collection of packages that help you manage the versioning and releasing of packages in your monorepo. The packages include:
-
@turbo-version/turbo: A tool for managing the versioning of your monorepo packages. -
@turbo-version/release: A CLI tool for releasing packages in your monorepo.
To get started, check out the documentation for each package:
👨💻 We welcome contributions to Turbo Version! If you'd like to contribute, please read our contribution guidelines and follow our code of conduct.
🚀 Happy versioning and releasing!