Repository navigation
Commit 833fae4
authored
docs: say how to replace an older install before specify init (#5004)
* 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)
* 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: 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)1 parent e5714c6 commit 833fae4
2 files changed
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
82 | 87 | | |
83 | 88 | | |
84 | 89 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
| 53 | + | |
| 54 | + | |
53 | 55 | | |
54 | 56 | | |
55 | 57 | | |
| |||
0 commit comments