Answer: To change a release tag, navigate to the Actions tab, select the Release: Change Tags workflow, click Run workflow, and fill in the required inputs (Version, Channel, Dry Run, Environment) before clicking Run workflow. The workflow then runs npm dist-tag add for the gemini-cli, gemini-cli-core and gemini-cli-a2a-server packages. Status: Confirmed Entry: tool/gemini-cli/admin-and-enterprise/change-release-tag Revision: 1 Digest: sha256:5dec9997f37d692e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:55Z Last changed: 2026-11-13T03:18:55Z Last verified: 2026-11-20T12:53:44Z Next check: 2026-11-21T12:53:44Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of workflow name | Release: Change Tags | [1] | 2026-11-20 version example | 0.5.0-preview-2 | [1] | 2026-11-20 channel examples | preview | [1] | 2026-11-20 dry run default | true | [1] | 2026-11-20 default environment | prod | [1] | 2026-11-20 command run | npm dist-tag add | [1] | 2026-11-20 Sources: [1] Google. "Gemini CLI releases". https://geminicli.com/docs/releases.md Role: primary. Accessed: 2026-11-20T12:53:44Z Quote: "Select the **Release: Change Tags** workflow from the list." (Supports: workflow name) Quote: "for example, `0.5.0-preview-2`" (Supports: version example) Quote: "The npm `dist-tag` to apply (for example, `preview`," (Supports: channel examples) Quote: "Leave as `true` to log the action without making changes" (Supports: dry run default) Quote: "`prod` is the default and will require authorization from a" (Supports: default environment) Quote: "The workflow will then run `npm dist-tag add` for the appropriate `gemini-cli`," (Supports: command run) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: d6da9eea721393570955f6bf54788ea66a6ee9cebf94ee293345425abd3d0659 (captured 2026-11-13T03:18:54Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:18:55Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:53:44Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:53:44Z Last attempt: 2026-11-20T12:53:44Z Notes and limitations: Extracted automatically from a single official source (section "How to change a release tag"). Related: https://latestn.com/tool/gemini-cli/admin-and-enterprise/create-manual-release How do I create a manual release for Gemini CLI? https://latestn.com/tool/gemini-cli/admin-and-enterprise/dev-vs-prod-environment What is the difference between the dev and prod environments for Gemini CLI releases? https://latestn.com/tool/gemini-cli/admin-and-enterprise/dogfooding-preview-tag How does Gemini CLI use dogfooding and the preview tag for release confidence? https://latestn.com/tool/gemini-cli/account-and-plans/paid-tier-higher-limits How can I get higher usage limits in Gemini CLI with a paid subscription? https://latestn.com/tool/gemini-cli/account-and-plans/supported-authentication-methods What authentication methods does Gemini CLI support? https://latestn.com/tool/gemini-cli/admin-and-enterprise/automated-release-gates What automated checks must pass before a Gemini CLI release is approved? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:55Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/admin-and-enterprise/change-release-tag/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/gemini-cli/admin-and-enterprise/change-release-tag POST: https://latestn.com/dispute/tool/gemini-cli/admin-and-enterprise/change-release-tag with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/admin-and-enterprise/change-release-tag?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I change a release tag for Gemini CLI? Revision 1, last verified 2026-11-20T12:53:44Z. https://latestn.com/tool/gemini-cli/admin-and-enterprise/change-release-tag (accessed 2026-11-21T10:01:52Z). @misc{LatestN_tool_gemini_cli_admin_and_enterprise_change_release_tag_r1, title = {How do I change a release tag for Gemini CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/admin-and-enterprise/change-release-tag}}, note = {Revision 1; digest sha256:5dec9997f37d692e; last verified 2026-11-20T12:53:44Z; accessed 2026-11-21T10:01:52Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/gemini-cli/admin-and-enterprise/change-release-tag