Skip to content

chore: update DocGuard extension to v0.25.0#2707

Merged
mnriem merged 1 commit into
github:mainfrom
raccioly:update-docguard
Jun 9, 2026
Merged

chore: update DocGuard extension to v0.25.0#2707
mnriem merged 1 commit into
github:mainfrom
raccioly:update-docguard

Conversation

@raccioly

@raccioly raccioly commented May 26, 2026

Copy link
Copy Markdown
Contributor

DocGuard community catalog update — v0.9.11 → v0.25.0

Updates the docguard entry in extensions/catalog.community.json to the current DocGuard release.

Changes

  • Version: 0.9.11 → 0.25.0
  • Download: spec-kit-docguard-v0.25.0.zip — published asset on the v0.25.0 release.
  • Description: "Zero NPM runtime dependencies" → "One pinned runtime dependency; pure Node.js otherwise." DocGuard added a single pinned dependency (@babel/parser) in v0.24 for AST-based traceability validation (JS/TS + Python).
  • Refreshed the catalog + entry updated_at timestamps.
  • Synced the matching row in docs/community/extensions.md.

Review items addressed

  • Conflicts resolved — branch rebased onto current main; the diff is now only the docguard block, the two updated_at timestamps, and the docs table row.
  • Version reconciled — title, description, catalog entry, and download URL all reference v0.25.0 (the earlier v0.21.1 / v0.23.0 mismatch Copilot flagged is gone).
  • Docs kept in syncdocs/community/extensions.md DocGuard 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

Copilot AI review requested due to automatic review settings May 26, 2026 16:15
@raccioly raccioly requested a review from mnriem as a code owner May 26, 2026 16:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 docguard extension version and updated its release download URL.
  • Updated updated_at timestamps for the catalog and the docguard entry.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 1

Comment thread extensions/catalog.community.json Outdated

@mnriem mnriem left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please resolve conflicts. Note going forward please use the extension submission issue template for adding/updating an extension. Thanks!

@raccioly raccioly changed the title chore: update DocGuard extension to v0.21.1 chore: update DocGuard extension to v0.22.0 May 28, 2026
Copilot AI review requested due to automatic review settings May 29, 2026 14:58
@raccioly raccioly changed the title chore: update DocGuard extension to v0.22.0 chore: update DocGuard extension to v0.22.1 May 29, 2026
@raccioly raccioly changed the title chore: update DocGuard extension to v0.22.1 chore: update DocGuard extension to v0.23.0 May 29, 2026
@mnriem mnriem requested review from Copilot and removed request for Copilot May 30, 2026 12:24

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 2

Comment thread extensions/catalog.community.json Outdated
Comment thread extensions/catalog.community.json Outdated
@mnriem

mnriem commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 2

Comment thread extensions/catalog.community.json
Comment thread extensions/catalog.community.json
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>
@raccioly raccioly changed the title chore: update DocGuard extension to v0.23.0 chore: update DocGuard extension to v0.25.0 Jun 8, 2026
@raccioly

raccioly commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

Addressed the review feedback:

  • Conflicts resolved — rebased onto current main. The diff is now just the docguard entry, the catalog/entry updated_at timestamps, and the matching docs/community/extensions.md row.
  • Version reconciled to v0.25.0 — title, description, catalog version, and download URL all match now (the v0.21.1 / v0.23.0 mismatch Copilot flagged is gone). The v0.25.0 release asset is published and verified.
  • Docs table synced with the catalog description.

Understood on the Extension Submission issue template — I'll route future DocGuard updates through it. Thanks @mnriem!

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new

@mnriem mnriem self-requested a review June 9, 2026 13:27
@mnriem mnriem merged commit 8373a60 into github:main Jun 9, 2026
11 checks passed
@mnriem

mnriem commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Thank you!

raccioly pushed a commit to raccioly/docguard that referenced this pull request Jun 9, 2026
…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
raccioly added a commit to raccioly/docguard that referenced this pull request Jun 9, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants