Answer: To release a Gemini CLI extension through a Git repository, create a public Git repository and provide the URL to your users, who can then install it using `gemini extensions install `. Users can optionally depend on a specific branch, tag, or commit using the `--ref` argument. Status: Confirmed Entry: tool/gemini-cli/integrations/release-extension-via-git Revision: 1 Digest: sha256:0ef77fc0579bec43 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:22Z Last changed: 2026-11-13T03:18:22Z Last verified: 2026-11-20T12:52:43Z Next check: 2026-11-21T12:52:43Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of install command | gemini extensions install | [1] | 2026-11-20 ref argument | --ref | [1] | 2026-11-20 example ref | stable | [1] | 2026-11-20 latest version commit | HEAD | [1] | 2026-11-20 release channels | stable | [1] | 2026-11-20 Sources: [1] Google. "Release extensions". https://geminicli.com/docs/extensions/releasing.md Role: primary. Accessed: 2026-11-20T12:52:43Z Quote: "They can then install your extension using `gemini extensions install `." (Supports: install command) Quote: "Users can optionally depend on a specific branch, tag, or commit using the `--ref` argument." (Supports: ref argument) Quote: "gemini extensions install --ref=stable" (Supports: example ref) Quote: "The `HEAD` commit is always treated as the latest version." (Supports: latest version commit) Quote: "You can use branches or tags to manage different release channels, such as `stable`, `preview`, or `dev`." (Supports: release channels) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: 6350690402f09294cd24f8bac3f2d0d974e47335127b3160d1391fc7dd453b7f (captured 2026-11-13T03:18:22Z) 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:22Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:52:43Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:52:43Z Last attempt: 2026-11-20T12:52:43Z Notes and limitations: Extracted automatically from a single official source (section "Release through a Git repository"). Related: https://latestn.com/tool/gemini-cli/integrations/release-extension-via-github-releases How do I release a Gemini CLI extension using GitHub Releases? https://latestn.com/tool/gemini-cli/integrations/use-core-package-standalone Can I use @google/gemini-cli-core as a standalone package in my own project? https://latestn.com/tool/gemini-cli/integrations/what-is-acp What is the Agent Client Protocol (ACP) and how does Gemini CLI use it? https://latestn.com/tool/gemini-cli/integrations/mcp-github-credentials What credentials does Gemini CLI need for the GitHub MCP server? https://latestn.com/tool/gemini-cli/integrations/package-hooks-as-extension How do I package Gemini CLI hooks as an extension? https://latestn.com/tool/gemini-cli/integrations/read-mcp-resource How do I read the content of a specific MCP resource by URI in Gemini CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:22Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/integrations/release-extension-via-git/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/integrations/release-extension-via-git POST: https://latestn.com/dispute/tool/gemini-cli/integrations/release-extension-via-git with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/integrations/release-extension-via-git?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I release a Gemini CLI extension through a Git repository? Revision 1, last verified 2026-11-20T12:52:43Z. https://latestn.com/tool/gemini-cli/integrations/release-extension-via-git (accessed 2026-11-21T09:55:15Z). @misc{LatestN_tool_gemini_cli_integrations_release_extension_via_git_r1, title = {How do I release a Gemini CLI extension through a Git repository?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/integrations/release-extension-via-git}}, note = {Revision 1; digest sha256:0ef77fc0579bec43; last verified 2026-11-20T12:52:43Z; accessed 2026-11-21T09:55:15Z} } 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/integrations/release-extension-via-git