release: v0.25.1 — fix spec-kit extension duplicate-alias install failure (#229)#240
Merged
Conversation
… via submission issue template Fixes #229. The spec-kit extension manifest declared `aliases` identical to their own command names (guard/fix/review/score). spec-kit registers the name and each alias in one namespace, so a name-equal alias self-collides and is rejected as a duplicate command — blocking install/update on v0.23.0–v0.25.0. Removed the four self-referential aliases. Also reworks the spec-kit catalog publish triggers per maintainer guidance (github/spec-kit#2707) and the Extension Publishing Guide: catalog add/update must go through the Extension Submission issue template, submitted through the form UI (so labels/assignment auto-apply) — not a direct PR editing catalog.community.json. The release pipeline (`sync-catalog` job) and the manual recovery workflow now call speckit-submission.py to build a prefilled issues/new?template URL plus a paste-fallback body, and open a one-click reminder issue in THIS repo. No writes to github/spec-kit, no PR, no fork sync. Removes the orphaned patch-catalog.py; SPECKIT_PR_TOKEN is no longer used. https://claude.ai/code/session_01TmB4nnpuz6WEv1iNYdmFrM
…lure (#229) Bumps package.json, pyproject.toml, and the extension manifest to 0.25.1 and adds the CHANGELOG entry for the #229 fix (removed self-referential command aliases) and the catalog-publishing rework (github/spec-kit#2707). Merging this to main triggers the release pipeline (tag, GitHub Release, npm, PyPI, extension ZIP) and the sync-catalog job that produces the prefilled Extension Submission form link. https://claude.ai/code/session_01TmB4nnpuz6WEv1iNYdmFrM
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
2 participants
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.
Summary
Fixes #229 and reworks spec-kit catalog publishing per maintainer guidance. Merging this to
maintriggers the release pipeline (tag → GitHub Release → npm → PyPI → extension ZIP → catalog-submission link).The bug (#229)
specify extension add/update docguardfailed withValidation Error: Duplicate command or alias 'speckit.docguard.guard'on v0.23.0–v0.25.0. Theextension.ymlmanifest declaredaliasesidentical to their own command names (guard,fix,review,score). spec-kit registers the command name and each alias in one namespace, so a name-equal alias self-collides and is rejected as a duplicate. Fix: removed the four self-referential aliases.Catalog publishing rework (github/spec-kit#2707)
The maintainer asked that catalog add/update go through the Extension Submission issue template, not a direct PR against
catalog.community.json. The Extension Publishing Guide also requires it be submitted through the form UI (so labels auto-apply and a maintainer is auto-assigned)..github/scripts/speckit-submission.pyproduces a prefilledissues/new?template=…URL (--url) plus a paste-fallback body (--body), values defined once so they can't drift.release.ymlsync-catalogand the manualsync-speckit-catalog.ymlnow open a one-click reminder issue in this repo with that link — no writes togithub/spec-kit, no PR.patch-catalog.py;SPECKIT_PR_TOKENis no longer used by these workflows.Version
Bumped to 0.25.1 in
package.json,pyproject.toml, andextension.yml; CHANGELOG updated.Testing
Full suite: 745/765 pass. The 20 remaining failures are git-history/rename-tracking suites (
shared-git,Freshness,impact,sync --since, test-discovery) that require a full clone; they fail only in the shallow sandbox and pass in release CI (fetch-depth: 0). No failures relate to this change (diff is YAML/Python/CHANGELOG/version strings only).After merge
The
sync-catalogjob will open a reminder issue containing the valid prefilled submission link for v0.25.1. I'll follow up on #229 once npm/PyPI publish so the reporter can verifyspecify extension update docguard.https://claude.ai/code/session_01TmB4nnpuz6WEv1iNYdmFrM
Generated by Claude Code