Conversation
Bumps the three community catalog entries from v0.4.12 to v0.5.1, the current release. One PR rather than three because the bundle pins its component versions and a partial bump breaks `bundle install` resolution. bundle 0.4.12 -> 0.5.1 extension 0.4.12 -> 0.5.1, provides.commands 2 -> 5 preset 0.4.12 -> 0.5.1 The extension's command count has been stale since v0.4.13: `dig`, `matrix` and `portfolio` shipped after the 0.4.12 entry was written. Every new download_url was fetched and returns 200. Digests of the three published archives, computed from the v0.5.1 tag: 962421be236991f5afa4a93f48bd16a9b2e61cd9221985b9f233b93407132246 specassay-0.5.1.zip 874728251c850e84d71f7a94dbdc326073703a8b408690d87a62b68d43dc6eff specassay-check-0.5.1.zip 41e5b5e807bbb2b7d4d90253886122416109465af023d85a110cd522c16848fc specassay-preset-0.5.1.zip Tested on Spec Kit 1.0.5 on 2026-09-20: install through a curated catalog, Gate run, ID mint, and the Gate's refusal of the freshly minted ID, then cleared to green as tracked debt. Supersedes github#4448, which proposed v0.4.13 and is now two releases behind.
7 tasks
Author
|
Closing this myself: per CONTRIBUTING.md, catalog updates go through the submission issues, not a direct catalog edit. Filing the Extension, Preset, and Bundle update issues instead. Sorry for the noise. |
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
1 participant
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.
Bumps the three SpecAssay community catalog entries from v0.4.12 to v0.5.1.
One PR rather than three because the bundle pins its component versions; a partial bump breaks bundle install resolution.
Nine changed lines, all inside the specassay / specassay-check entries. The extension's command count has been stale since v0.4.13: dig, matrix and portfolio shipped after the 0.4.12 entry was written.
Digests, computed from the tag
All three match the digests recorded in the project's own release evidence on 2026-09-17, independently re-derived today. Every new download_url was fetched: all return 200.
Tested on Spec Kit 1.0.5, 2026-09-20
Clean project,
specify init . --here --force --non-interactive --integration claude, then the curated catalog sources andspecify bundle install specassay:Gate, mint, and refusal on that same project:
Scope of this change
The community catalog is discovery-only, so this PR does not make
specify bundle install specassaywork from it, and is not claiming to. What it fixes is discovery: todayspecify bundle info specassayon a clean project answers v0.4.12 and offers a v0.4.12 download URL, three releases behind. Installation is from curated, install-allowed catalogs, as documented in the project's README.Supersedes #4448
#4448 proposed v0.4.13 and is now two releases behind. This PR replaces it; #4448 can be closed.