[community] Update SpecAssay to v0.4.13 (extension, preset, bundle) - #4448
Open
rdryfoos wants to merge 1 commit into
Open
[community] Update SpecAssay to v0.4.13 (extension, preset, bundle)#4448rdryfoos wants to merge 1 commit into
rdryfoos wants to merge 1 commit into
Conversation
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.
Description
Version-bump for the three SpecAssay community catalog entries, from v0.4.12 to v0.4.13:
specassay-check(extension),specassay(preset), andspecassay(bundle). Same fields the previous update PRs changed (#4254, #4256, #4257):version,download_url,updated_at, plus the extension'sprovides.commands(2 to 5; the extension has shipped five commands since dig, matrix, and portfolio landed). All three move together in one PR because the bundle pins its component versions; bumping one entry alone would makespecify bundle install specassayfail resolution.Release: https://github.com/rdryfoos/specassay/releases/tag/v0.4.13 (tag
105c4845f8ae88f1af361d56c0de458089b50fad, built and published by the repo's Release workflow). Asset digests, as reported by GitHub's release API and re-verified by download:specassay-check-0.4.13.zip:sha256:d7ac14c271b99aff0b649def9c3444b6e03090649df43ea2b9c3949ded91ed9fspecassay-preset-0.4.13.zip:sha256:ed4298d72b80f083400c0ac7bcbf9a3eb5d5950eb50abd542e8fc4b5b77d8a58specassay-0.4.13.zip:sha256:8529e8b7542a712542321856368b4f3d7f2f820f98350f7c7f7115670005f18dWhat v0.4.13 changes for a first-time installer, briefly: the Gate detects
python3orpython(Windows Git Bash works), reports its config state on startup, and explains what to do when the registry is empty instead of printing a bare OK. Full notes: https://github.com/rdryfoos/specassay/blob/main/CHANGELOG.md. The submission-form issues with the complete test evidence for this version will follow per the publishing guides; this PR is only the catalog pointer, so people installing from the community catalog stop landing on the version whose cold-install dead end v0.4.13 fixes.Testing
specify initproject, catalogs added install-allowed,specify bundle install specassayat 0.4.13: 2 components installed,specify extension listreports v0.4.13 withCommands: 5 | Hooks: 1.specify bundle update specassaymoves both components to v0.4.13 with the user's edited config preserved.uv run specify --help(not applicable: JSON catalog data only)uv sync && uv run pytest(not applicable: JSON catalog data only)AI Disclosure
Claude Code (Anthropic) prepared the JSON edits and this PR text under the maintainer's direction; the release, digests, and install tests were run and verified by the same session against the real CLI.