fix(catalog): companion → README docs, stable download URL, v0.4.1, sharper tags#2954
Open
alfredoperez wants to merge 3 commits into
Open
fix(catalog): companion → README docs, stable download URL, v0.4.1, sharper tags#2954alfredoperez wants to merge 3 commits into
alfredoperez wants to merge 3 commits into
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) <noreply@anthropic.com>
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
alfredoperez
changed the title
…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).
Comment on lines
+777
to
+778
| "version": "0.4.1", | ||
| "download_url": "https://github.com/alfredoperez/speckit-companion/releases/download/companion-latest/companion.zip", |
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.Changes
documentation→ points at the extensionREADME.mdso the catalog page renders the README (original fix).download_url→ the stable rollingcompanion-latest/companion.zipasset instead of a version-pinned release URL. This meansspecify extension add companionalways installs the newest build, and the catalog never needs a per-release PR just to bump the URL.version0.3.0→0.4.1(current release).tagssharpened for discovery — dropped the redundantcompanion(the id itself),progress, andlifecycle; addedspec-driven-development,spec-kit,turbo, andcapture. New set:spec-driven-development,spec-kit,tracking,turbo,capture,vscode,resume.The
companion-latestasset is a permanent prerelease that's force-refreshed on every release, so the catalog entry stays correct as the extension updates.