From 7d308a470751721a2527975ff2911012582e8ac8 Mon Sep 17 00:00:00 2001 From: kartsan03 Date: Sat, 17 Oct 2026 10:27:28 +0000 Subject: [PATCH 1/3] docs: say how to replace an older install before specify init `uv tool install specify-cli` keeps an already installed specify-cli, so a machine with an old CLI (0.1.6 in #4994) keeps it and `specify init` fails. Note the --force/--upgrade commands next to the install commands. Refs #4994 Assisted-by: Claude Code (model: claude-opus-5-5, autonomous) --- README.md | 4 ++++ docs/installation.md | 2 ++ 2 files changed, 6 insertions(+) diff --git a/README.md b/README.md index e06db3ec49..123cb5bcbf 100644 --- a/README.md +++ b/README.md @@ -79,6 +79,10 @@ specify init my-project --integration copilot cd my-project ``` +If Spec Kit is already installed, `uv tool install specify-cli` keeps the installed +version. Check with `specify version`, and if it's older, run +`uv tool install --force specify-cli` before `specify init`. + The examples use **GitHub Copilot's default skills mode**. Replace `copilot` with diff --git a/docs/installation.md b/docs/installation.md index b68a65d241..2a887b6505 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -50,6 +50,8 @@ pipx install specify-cli pip install specify-cli ``` +If `specify-cli` is already installed, these commands keep the installed version, even when a newer release exists. Run `specify version` to check. To replace an older install, run `uv tool install --force specify-cli`, `pipx install --force specify-cli` or `pip install --upgrade specify-cli`. An old CLI can't set up projects from current releases: with 0.1.6, for example, `specify init --integration ...` fails with `No such option: --integration`, and `specify init --ai ...` fails with `No matching release asset found`. + To install a specific release, pin the version — for example `uv tool install specify-cli==0.12.11`. See the [PyPI installation guide](install/pypi.md) for details, including how to upgrade and how to [install from a custom or private package index](install/pypi.md#install-from-a-custom-or-private-package-index). ### One-time Usage From 7bab9c8cc54de4fa29e360d1cf2b58a14279468e Mon Sep 17 00:00:00 2001 From: kartsan03 Date: Mon, 19 Oct 2026 16:59:04 +0000 Subject: [PATCH 2/3] docs: replace an older install with the tool that made it `pip install --upgrade specify-cli` doesn't replace a `uv tool` install, so the old `specify` can stay first on PATH and `specify init` keeps failing. Say to use the same tool as the original install, as docs/install/pypi.md already does for upgrades. Refs #4994 Assisted-by: Codex CLI (model: gpt-6.1-sol, autonomous) Assisted-by: Claude Code (model: claude-opus-5-5, autonomous) --- docs/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/installation.md b/docs/installation.md index 2a887b6505..a9f7dfc1f1 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -50,7 +50,7 @@ pipx install specify-cli pip install specify-cli ``` -If `specify-cli` is already installed, these commands keep the installed version, even when a newer release exists. Run `specify version` to check. To replace an older install, run `uv tool install --force specify-cli`, `pipx install --force specify-cli` or `pip install --upgrade specify-cli`. An old CLI can't set up projects from current releases: with 0.1.6, for example, `specify init --integration ...` fails with `No such option: --integration`, and `specify init --ai ...` fails with `No matching release asset found`. +If `specify-cli` is already installed, these commands keep the installed version, even when a newer release exists. Run `specify version` to check. To replace an older install, use the same tool as the original install: `uv tool install --force specify-cli`, `pipx install --force specify-cli` or `pip install --upgrade specify-cli`. A different tool can install a second copy and leave the old `specify` first on `PATH`. An old CLI can't set up projects from current releases: with 0.1.6, for example, `specify init --integration ...` fails with `No such option: --integration`, and `specify init --ai ...` fails with `No matching release asset found`. To install a specific release, pin the version — for example `uv tool install specify-cli==0.12.11`. See the [PyPI installation guide](install/pypi.md) for details, including how to upgrade and how to [install from a custom or private package index](install/pypi.md#install-from-a-custom-or-private-package-index). From 0635468d4eeea6a35b9ded34a4c3fa56a4e00aa7 Mon Sep 17 00:00:00 2001 From: kartsan03 Date: Mon, 19 Oct 2026 17:22:26 +0000 Subject: [PATCH 3/3] docs: point the version check at the latest release on PyPI `specify version` only prints the installed version, so "if it's older" left the comparison to the reader. Link the latest specify-cli release on PyPI in both notes and say to compare against it. Refs #4994 Assisted-by: Codex CLI (model: gpt-6.1-sol, autonomous) Assisted-by: Claude Code (model: claude-opus-5-5, autonomous) --- README.md | 5 +++-- docs/installation.md | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 123cb5bcbf..1bd6a2c106 100644 --- a/README.md +++ b/README.md @@ -80,8 +80,9 @@ cd my-project ``` If Spec Kit is already installed, `uv tool install specify-cli` keeps the installed -version. Check with `specify version`, and if it's older, run -`uv tool install --force specify-cli` before `specify init`. +version. Compare the version shown by `specify version` with the +[latest version on PyPI](https://pypi.org/project/specify-cli/), and if it's older, +run `uv tool install --force specify-cli` before `specify init`. diff --git a/docs/installation.md b/docs/installation.md index a9f7dfc1f1..ba61ab9452 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -50,7 +50,7 @@ pipx install specify-cli pip install specify-cli ``` -If `specify-cli` is already installed, these commands keep the installed version, even when a newer release exists. Run `specify version` to check. To replace an older install, use the same tool as the original install: `uv tool install --force specify-cli`, `pipx install --force specify-cli` or `pip install --upgrade specify-cli`. A different tool can install a second copy and leave the old `specify` first on `PATH`. An old CLI can't set up projects from current releases: with 0.1.6, for example, `specify init --integration ...` fails with `No such option: --integration`, and `specify init --ai ...` fails with `No matching release asset found`. +If `specify-cli` is already installed, these commands keep the installed version, even when a newer release exists. Compare the version shown by `specify version` with the [latest version on PyPI](https://pypi.org/project/specify-cli/). To replace an older install, use the same tool as the original install: `uv tool install --force specify-cli`, `pipx install --force specify-cli` or `pip install --upgrade specify-cli`. A different tool can install a second copy and leave the old `specify` first on `PATH`. An old CLI can't set up projects from current releases: with 0.1.6, for example, `specify init --integration ...` fails with `No such option: --integration`, and `specify init --ai ...` fails with `No matching release asset found`. To install a specific release, pin the version — for example `uv tool install specify-cli==0.12.11`. See the [PyPI installation guide](install/pypi.md) for details, including how to upgrade and how to [install from a custom or private package index](install/pypi.md#install-from-a-custom-or-private-package-index).