Blazing fast intelligent monorepo continuous integration versioning.
In-Development of Beta
Large file system directory structures are scanned using Rust Rayon to minimize scan times.
Package versions are validated to prevent duplicate target versions and variance from versioning scheme.
Repository versions are automatically derived from package versions.
Supports versioning of repository packages using standard package management configuration files.
See target.json for complete list of supported files.
Cannot find your favorite package manager? Open an issue to request support.
These files are used for monover
to decide how to increment package version files.
"major"
"minor"
"patch"
"<major|minor>-<pre-release-name>"
These are special files that have three main functions:
- Version repository (auto-generated).
- Version repository packages (overrides version file matches).
- Settle version ambiguity (1 < version file match).
The format for VERSION
files is a simple double-quoted string. They are valid JSON files without file extensions.
There are two possible values for the VERSION
file string.
"1.0.0"
Must match a file key in targets.json.
"cargo.toml"
Use this option for version ambiguity due to multiple files in targets.json found in single package.