Commands

chamoji next-version

Print the next version, worked out from the commits since the last release tag. It doesn’t check the branch or touch your files, and in a single package it doesn’t fetch. When no commit calls for a release, it prints nothing to stdout and exits 3.

What it does, in order

1. Finds the last release. The newest release tag in the history of HEAD, or of the ref you give with --to.
2. Reads the commits since. Each gitmoji has a bump: ✨ is minor, 🐛 is patch, 💥 is major. A breaking change is always major. The largest one wins.
3. Prints the version. Without a v, such as 0.2.0, and exits 0. When no commit implies a bump, as with only docs, tests or refactors, it says so on stderr and exits 3.

In a repo with release units, it does this for each unit, with the unit’s own tags and commits, and prints one line per unit. A unit with no tag of its own gets its firstVersion when that’s set, or else the version in its manifest, or a date version for a calver unit. Settings such as zeroMajor and a unit’s versioning change how its version moves; Config has them.

With release units it needs the full history. In a shallow clone, such as the one GitHub Actions’ checkout makes by default, it first fetches every commit and tag from origin, and exits 2 when it can’t. In CI, check out with fetch-depth: 0.

Arguments

chamoji next-version takes no arguments.

Flags

Common combinations

In a release script, exit 3 stops the chain before anything is written:

version=$(chamoji next-version) && chamoji changelog --release "$version" -o CHANGELOG.md

Output

These are from real runs. In widgets, a single package with a ✨ and a 🐛 since v0.1.0:

0.2.0

After a release, with only a 📝 commit since, it exits 3:

chamoji: no release needed (no commits since the last tag imply a version bump)

In shop, whose two apps release on their own. web has a fix since web/v1.2.0, and mobile has no tag yet, so it takes the version in its package.json:

mobile: 1.0.0
web: 1.2.1

{
  "units": [
    {
      "unit": "mobile",
      "version": "1.0.0",
      "own": 2,
      "shared": 2
    },
    {
      "unit": "web",
      "version": "1.2.1",
      "own": 1,
      "shared": 1
    }
  ]
}

When no unit would release, each line says why, and it exits 3:

mobile: nothing to release
web: no release needed (1 change of its own doesn't need one)

In a repo with two or more apps under apps/ and no release section, the first run in each clone suggests setup, on stderr:

chamoji: this looks like a monorepo with several apps; run chamoji setup to version each one
0.1.0

Exit codes

Exit codes has every command’s codes.

Related