chore: update DocGuard extension to v0.25.0#2707
Conversation
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 community extensions catalog metadata to reflect a new docguard release and refreshes the catalog timestamps.
Changes:
- Bumped
docguardextension version and updated its release download URL. - Updated
updated_attimestamps for the catalog and thedocguardentry.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mnriem
left a comment
There was a problem hiding this comment.
Please resolve conflicts. Note going forward please use the extension submission issue template for adding/updating an extension. Thanks!
|
Please address Copilot feedback and resolve conflicts. After merging this PR I would recommend any new/updated extensions submission to go through the extension submission issue template so you do not have to deal with so much back and forth. |
Bump the docguard community catalog entry 0.9.11 -> 0.25.0, point the download at the v0.25.0 release asset, and update the description to reflect the single pinned runtime dependency (@babel/parser, added in v0.24 for AST-based validation). Sync the docs/community table row to match. Rebased onto current main to clear the prior merge conflict. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Addressed the review feedback:
Understood on the Extension Submission issue template — I'll route future DocGuard updates through it. Thanks @mnriem! |
|
Thank you! |
…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
…lure (#229) * fix(extension): drop duplicate command aliases; route catalog updates 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 * chore(wolf): session bookkeeping (memory/ledger/session) https://claude.ai/code/session_01TmB4nnpuz6WEv1iNYdmFrM * release: v0.25.1 — fix spec-kit extension duplicate-alias install failure (#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 * chore(wolf): session bookkeeping for v0.25.1 / #229 work https://claude.ai/code/session_01TmB4nnpuz6WEv1iNYdmFrM --------- Co-authored-by: Claude <noreply@anthropic.com>
DocGuard community catalog update — v0.9.11 → v0.25.0
Updates the
docguardentry inextensions/catalog.community.jsonto the current DocGuard release.Changes
spec-kit-docguard-v0.25.0.zip— published asset on the v0.25.0 release.@babel/parser) in v0.24 for AST-based traceability validation (JS/TS + Python).updated_attimestamps.docs/community/extensions.md.Review items addressed
main; the diff is now only thedocguardblock, the twoupdated_attimestamps, and the docs table row.docs/community/extensions.mdDocGuard row now matches the JSON description.Process note
@mnriem — understood on routing future updates through the Extension Submission issue template; I'll use that flow for the next bump. Thanks for the patience here.
Repository: https://github.com/raccioly/docguard