Closed
Clarify installation verification guidance for Spec Kit#3532
Conversation
Copilot
AI
changed the title
[WIP] Fix code based on review comments
Clarify installation verification guidance for Spec Kit
Jul 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies that specify version reports version/runtime details but cannot establish installation provenance.
Changes:
- Adds provenance guidance for uv and pipx installs.
- Documents pinned versus unpinned pipx upgrades.
Show a summary per file
| File | Description |
|---|---|
docs/installation.md |
Revises general verification guidance. |
docs/install/pipx.md |
Adds pipx provenance and upgrade notes. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 3
- Review effort level: Medium
| ``` | ||
|
|
||
| This helps verify you are running the official Spec Kit build from GitHub, not an unrelated package with the same name. | ||
| This is a version/runtime check. It helps confirm the installed Spec Kit CLI version and environment, but it does not prove the executable came from the official GitHub release source or another install source. If you need to confirm install provenance, inspect the package manager's stored install metadata (for example, `uv tool list` or `pipx list`, depending on how you installed Spec Kit). |
| specify version | ||
| ``` | ||
|
|
||
| `specify version` reports the installed Spec Kit CLI version and runtime details. It is a useful version/runtime check, but it does not prove whether the executable came from a Git source, a PyPI package, or another location. If you need to confirm installation provenance, inspect the package manager's stored install metadata (for example, `pipx list` for `pipx`-managed installs). |
| pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z | ||
| ``` | ||
|
|
||
| If you want to move to the latest release instead of a pinned tag, omit the `@vX.Y.Z` suffix from the install command above. |
Collaborator
|
Tracked by #3516 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The installation docs were implying that
specify versioncould verify install provenance. That is misleading: the command reports local CLI version and runtime details, but it does not establish whether the executable came from the official GitHub release source, PyPI, or another location.specify versionas a version/runtime check and to point readers to package-manager metadata (for example,uv tool listorpipx list) when they need to verify how Spec Kit was installed.pipx installmoves the install to the latest release rather than a pinned version.