fix(catalog): companion → README docs, version-pinned download URL, v0.11.0, refreshed tags#2954
Merged
mnriem merged 8 commits intoJun 26, 2026
Conversation
The companion entry's documentation URL pointed at a directory (speckit-extension/docs/), which the community site can't fetch as markdown — its extension page renders an empty README (readmeContent: null). Every other catalog entry points documentation at a specific README.md (or .md file). Point companion at its extension README so the page renders. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Speckit Companion entry in the community extensions catalog to point users to the correct documentation page.
Changes:
- Changed the
documentationURL from a docs directory listing to the extensionREADME.md.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…1, sharper tags - download_url now points at the rolling companion-latest asset so by-name install always serves the newest build (no per-release catalog PR) - version 0.3.0 → 0.4.1 - tags: drop redundant 'companion'/'progress'/'lifecycle', add spec-driven-development, spec-kit, turbo, capture
…atus, resume, configurable, extensible) Tags now name what Companion adds over stock spec-kit, in browse-able terms — dropped catalog-noise (spec-kit, spec-driven-development) and insider jargon (turbo, capture).
Pin download_url to the version-matched release asset (every other catalog entry pins to a tag; the floating companion-latest URL made installs non-reproducible). Bring the entry up to v0.8.0: version 0.4.1 -> 0.8.0, commands 10 -> 12, speckit_version floor >=0.9.5.dev0, and drop the removed "turbo pipeline profile" from the description in favor of the hooks/recipes customization that shipped. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Collaborator
|
Please address Copilot feedback |
Contributor
Author
|
Pushed a round of fixes addressing the review:
PR title and description updated to match the final state. Thanks for the careful pass. |
Contributor
Author
|
@mnriem it should be good now =) Thank you! |
Collaborator
|
Thank you! |
kanfil
added a commit
to tikalk/agentic-sdlc-spec-kit
that referenced
this pull request
Jun 29, 2026
Merge github/spec-kit 0.11.8 -> 0.11.9 (15 commits). Key upstream changes: - fix(extensions): tell agent to run mandatory hooks (github#2901) - fix(scripts): keep PowerShell branch-name acronym case-sensitive (github#3129) - fix(extensions,presets,workflows): resolve GHES private release assets (github#3157) - fix(catalog): companion docs, version-pinned URL, refreshed tags (github#2954) - Add community bundle submission path (github#3162) - Docs: document missing flags --force and --refresh-shared-infra (github#3179) Fork customizations preserved: - Phase A/B + Mission Brief in core specify.md - spec.* command aliases, orange theming - Bundled extensions/presets, enhanced hook dispatcher - Bundled-extension preferred update path (install_from_directory) - Git extension opt-in (aligned with upstream) Fork bug fixes: - Relative imports in extensions/ and presets/ __init__.py - registered.append guard in agents.py - Bundled update now uses install_from_directory, not catalog download
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.
Updates the
companion(SpecKit Companion) community-catalog entry. This started as a one-line docs fix and grew through review into a full refresh of the entry to the current release. The summary below reflects the final state of the entry.Changes
documentation→ now points at the extensionREADME.md(a single fetchable markdown file) instead of a directory URL. The catalog consumer (speckit-community.github.io) renders this field as one markdown file; a directory URL yielded a blank page.companionwas the only entry pointing at a directory.download_url→ version-pinned to the release assetspeckit-ext-v0.11.0/companion-0.11.0.zip(returns 200), so the declaredversionand the downloaded bits always agree. This matches every other catalog entry (all pin to a tag). Thecompanion-latestrolling tag still exists for our own install scripts, but the catalog is version-pinned, which is the right semantics here.version0.3.0→0.11.0(latest released build).provides.commands10→13(matches what ships in v0.11.0).requires.speckit_version>=0.8.5→>=0.9.5(bare floor, matching the rest of the catalog). A.dev0suffix would only affect users running a pre-release of the exact floor version (0.9.5.devN), which never shipped stable and is moot now that Spec Kit is at 0.11.x — newer dev builds already satisfy a bare floor.tagsrefreshed for discovery. Final set:vscode,progress,status,resume,configurable,extensible.The catalog entry tracks the latest published release (v0.11.0). Going forward, the release flow bumps this entry automatically on each new release, so it won't drift.