Evidence record / gemini-cli
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-08-10-gemini-cli-stable-version-numbers-went-discontinuous-0-54-0-to-0-54-4-in-27-hours
Stable version numbers went discontinuous: 0.54.0 to 0.54.4 in 27 hours, 0.54.1-0.54.3 never published.
v0.54.4 published 2026-08-07T04:44Z, 27 hours after v0.54.0. Its entire content is one cherry-picked fix (#28700, stopping a new user message from fusing into an unanswered tool response) plus a version bump to 0.54.2 and a revert of that bump. The intervening patch numbers were burned by release-machinery churn, not by shipped code; neither GitHub nor npm has 0.54.1, 0.54.2, or 0.54.3. In the same window #28694 landed to handle npm dist-tag deletion failures on registries that forbid it, and npm still carries a stray dist-tag literally named false pointing at a May 2026 nightly.
Channel: tagged-release. Ancestry: gh api repos/google-gemini/gemini-cli/tags contains v0.54.0 and v0.54.4 with no v0.54.1/.2/.3. npm view @google/gemini-cli versions likewise jumps 0.54.0 -> 0.54.4. git log v0.54.0..v0.54.4 returns exactly 5 commits: one cherry-pick (#28710), a bump to 0.54.2 (#28712), a revert of that bump (#28715), and two release chores.
Operator consequence: Ignore for behaviour; adapt your tooling. Any policy that infers 'how much changed' from patch distance, or that enumerates intermediate versions to build an upgrade path, will break on this line -- three of the four patch numbers do not exist. Pin exact versions and diff by git range, not by semver arithmetic.
Receipt
Finding metadata
Run: 2026-08-10-weekly-digest-2026-08-03_2026-08-10-frontier-v0
Finding ID: 2026-08-10-gemini-cli-stable-version-numbers-went-discontinuous-0-54-0-to-0-54-4-in-27-hours
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact