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-10-24-gemini-cli-preview-checks-whether-an-automatic-update-changed-the-active-installation
Preview checks whether an automatic update changed the active installation. The updater resolves the running CLI’s path before updating, then checks the package metadata beside that installation. If the matching package still has a lower version than the intended update, it emits update-failed with a PATH-shadowing explanation instead of success. Missing or unreadable metadata remains a best-effort boundary: the check is not fail-closed attestation.
Channel: preview-or-beta. Half: both. Date: 2026-10-16.
Operator consequence: On preview, a successful package-manager exit is less likely to conceal an unchanged active CLI. Keep recording the resolved executable and its version in deployment receipts, especially with several Node installations. The repair removes one misleading success signal but does not turn automatic updates into pinned, reproducible deployment.
Receipt
Finding metadata
Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0
Finding ID: 2026-10-24-gemini-cli-preview-checks-whether-an-automatic-update-changed-the-active-installation
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-24-gemini-cli-preview-checks-whether-an-automatic-update-changed-the-active-installationgithub.com/google-gemini/gemini-cli/commit/49797afb4d323b70a4fd30ee89aeb8faba399f90tagged commit file2026-10-24-gemini-cli-preview-checks-whether-an-automatic-update-changed-the-active-installationgoogle-gemini/gemini-cli / packages/cli/src/utils/handleAutoUpdate.ts
Versioned source: run artifact