OneUp CalVer Manager FAQs

Question 1

What is the philosophy behind OneUp?

Accepted Answer

OneUp treats versions as release artifacts rather than source code. This means you don't need to manually update or commit version numbers in Git; the version is calculated and injected at the time of release.

Question 2

Does OneUp require a specific version format?

Accepted Answer

No, it supports various CalVer tokens including YYYY, YY, MM, DD, and MICRO. The default format is YY.MM.MICRO, but it can be fully customized.

Question 3

Which file types does OneUp support?

Accepted Answer

It automatically detects and updates package.json for Node.js projects and Cargo.toml for Rust projects. You can also specify custom target paths using the --target option.

Question 4

How does OneUp calculate the 'MICRO' version?

Accepted Answer

It queries the registry (like npm or crates.io) for existing versions matching today's date prefix, finds the highest MICRO value, and increments it by one.

Question 5

Can I use OneUp in my CI/CD pipeline?

Accepted Answer

Yes, OneUp is designed for CI environments. It calculates the version, updates the necessary files, and prints the final version to stdout for easy use in tagging and publishing commands.

OneUp CalVer Manager

Key Features

Use Cases

OneUp CalVer Manager

Key Features

Use Cases