Answer: To release a Gemini CLI extension via GitHub Releases, attach custom archives directly to your GitHub Release as assets, following the required archive structure with gemini-extension.json at the root. Gemini CLI checks for updates by looking for the Latest release on GitHub, and users can install specific versions using the --ref argument with a release tag. Status: Confirmed Entry: tool/gemini-cli/integrations/release-extension-via-github-releases Revision: 1 Digest: sha256:382fa2c10503baac (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:23Z Last changed: 2026-11-13T03:18:23Z Last verified: 2026-11-20T12:52:44Z Next check: 2026-11-21T12:52:44Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of distribution method | GitHub Releases | [1] | 2026-11-20 update check | Latest | [1] | 2026-11-20 specific version install | --ref | [1] | 2026-11-20 pre-release flag | --pre-release | [1] | 2026-11-20 required root file | gemini-extension.json | [1] | 2026-11-20 archive extensions | .tar.gz | [1] | 2026-11-20 platform values | darwin | [1] | 2026-11-20 arch values | x64 | [1] | 2026-11-20 Sources: [1] Google. "Release extensions". https://geminicli.com/docs/extensions/releasing.md Role: primary. Accessed: 2026-11-20T12:52:44Z Quote: "Distributing extensions through [GitHub Releases]" (Supports: distribution method) Quote: "Gemini CLI checks for updates by looking for the **Latest** release on GitHub." (Supports: update check) Quote: "Users can also install specific versions using the `--ref` argument with a release tag." (Supports: specific version install) Quote: "Use the `--pre-release` flag to install the latest version even if it isn't marked as **Latest**." (Supports: pre-release flag) Quote: "The `gemini-extension.json` file must be at the root of the archive." (Supports: required root file) Quote: "`{extension}`: Use `.tar.gz` or `.zip`." (Supports: archive extensions) Quote: "`{platform}`: Use `darwin` (macOS), `linux`, or `win32` (Windows)." (Supports: platform values) Quote: "`{arch}`: Use `x64` or `arm64`." (Supports: arch values) 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:23Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:52:44Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:52:44Z Last attempt: 2026-11-20T12:52:44Z Notes and limitations: Extracted automatically from a single official source (section "Release through GitHub Releases"). Related: 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/memory-and-context/auto-memory-limitations What are the limitations of Auto Memory in Gemini CLI? 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/gemini-cli/integrations/release-extension-via-git How do I release a Gemini CLI extension through a Git repository? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:23Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/integrations/release-extension-via-github-releases/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-github-releases POST: https://latestn.com/dispute/tool/gemini-cli/integrations/release-extension-via-github-releases 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-github-releases?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I release a Gemini CLI extension using GitHub Releases? Revision 1, last verified 2026-11-20T12:52:44Z. https://latestn.com/tool/gemini-cli/integrations/release-extension-via-github-releases (accessed 2026-11-21T10:01:05Z). @misc{LatestN_tool_gemini_cli_integrations_release_extension_via_github_releases_r1, title = {How do I release a Gemini CLI extension using GitHub Releases?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/integrations/release-extension-via-github-releases}}, note = {Revision 1; digest sha256:382fa2c10503baac; last verified 2026-11-20T12:52:44Z; accessed 2026-11-21T10:01:05Z} } 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-github-releases