From b8969cceffbbba58b228d9c9bf12bfdd236efb0b Mon Sep 17 00:00:00 2001 From: Pascal Birchler Date: Thu, 30 Oct 2025 18:24:48 +0100 Subject: [PATCH] fix(docs): remove incorrect extension install method (#11194) --- docs/extensions/extension-releasing.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/extensions/extension-releasing.md b/docs/extensions/extension-releasing.md index 29c19b8878..b2fa2d7833 100644 --- a/docs/extensions/extension-releasing.md +++ b/docs/extensions/extension-releasing.md @@ -15,11 +15,9 @@ if you need to ship platform specific binary files. This is the most flexible and simple option. All you need to do is create a publicly accessible git repo (such as a public github repository) and then users -can install your extension using `gemini extensions install `, or -for a GitHub repository they can use the simplified -`gemini extensions install /` format. They can optionally depend on a -specific ref (branch/tag/commit) using the `--ref=` argument, this -defaults to the default branch. +can install your extension using `gemini extensions install `. +They can optionally depend on a specific ref (branch/tag/commit) using the +`--ref=` argument, this defaults to the default branch. Whenever commits are pushed to the ref that a user depends on, they will be prompted to update the extension. Note that this also allows for easy rollbacks,