chore(catalog): bump v-model extension to v0.7.2#2613
Open
leocamello wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the community extension catalog metadata for the v-model extension to reference the upstream v0.7.1 release, keeping the catalog current for extension discovery and installation.
Changes:
- Bump
v-modelversion anddownload_urlto0.7.1/v0.7.1.zip. - Update
v-modelcapability counts (provides.commands/provides.hooks) to reflect the new release. - Refresh
starsandupdated_atfor thev-modelentry, and bump the top-level catalogupdated_at.
Show a summary per file
| File | Description |
|---|---|
| extensions/catalog.community.json | Updates the v-model extension entry (version, download URL, provides counts, stars, timestamps) and bumps the catalog timestamp accordingly. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 0
mnriem
requested changes
May 21, 2026
Collaborator
mnriem
left a comment
mnriem
left a comment
There was a problem hiding this comment.
Please resolve conflicts. Note going forward please use the extension submission issue. Thanks!
Updates the v-model entry in extensions/catalog.community.json to point at the new v0.7.2 release of leocamello/spec-kit-v-model: https://github.com/leocamello/spec-kit-v-model/releases/tag/v0.7.2 v0.7.0 and v0.7.1 were never submitted to this catalog individually, so this single bump catches the entry up from 0.6.0 directly to 0.7.2. version 0.6.0 -> 0.7.2 download_url v0.6.0.zip -> v0.7.2.zip commands 14 -> 17 (+3 bridge commands: plan / tasks / implement, added in v0.7.0) hooks 1 -> 4 (+3 lifecycle hooks: after_specify, before_implement, after_implement, added in v0.7.0) stars 21 -> 27 (live count from GitHub API) updated_at 2026-04-25 -> 2026-05-21 Top-level catalog `updated_at` matches upstream's current 2026-05-21 after rebase. Headline changes since v0.6.0: - v0.7.0: Bridge commands (plan / tasks / implement) and the four lifecycle hooks. The MF-1..MF-7 stabilization sprint (validators, splicer hardening, gate/guard scripts). - v0.7.1: Bridge command reconciliation toward "fully working and validated software." All 8 V-Model artefacts mandatory for implement; plan/tasks marked OPTIONAL; canonical-ID grammar generalised; AGENTS.md adopted; constitution v1.1.0. - v0.7.2: Extension packaging hygiene (`.extensionignore`); handoff graph documentation; template overlay mismatch resolved. Full release narratives at: https://github.com/leocamello/spec-kit-v-model/blob/v0.7.2/CHANGELOG.md
leocamello
force-pushed
the
chore/v-model-0.7.1
branch
from
17642c2 to
fa7db6a
Compare
leocamello
changed the title
Contributor
Author
|
Conflicts resolved against latest Meanwhile, v0.7.2 has shipped (https://github.com/leocamello/spec-kit-v-model/releases/tag/v0.7.2), so I've bumped this PR through to v0.7.2 directly rather than landing v0.7.1 only to immediately re-PR. The version delta is now:
Noted on the "extension submission issue" process for future submissions — will use that going forward. Thanks for the review! |
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.
Updates the
v-modelentry inextensions/catalog.community.jsonto point at the new v0.7.1 release.v0.7.0 was never submitted upstream, so this single bump catches the catalog up from
0.6.0directly to0.7.1. Follows the same pattern as the previous bumps:Catalog changes
versiondownload_urlprovides.commandsprovides.hooksstarsupdated_atTop-level catalog
updated_atbumped2026-05-15 → 2026-05-17.What's new since v0.6.0
v0.7.0 — Bridge Commands (catalog-relevant)
Three new commands and three new lifecycle hooks connect V-Model specification artifacts to executable implementation, completing the spec-to-code gap:
/speckit.v-model.plan/speckit.planplan.mdsynthesis with additive HTML-comment traceability; pinned-schema validation; structured run summary./speckit.v-model.tasks/speckit.tasksunit-test.md/integration-test.md/system-test.md/acceptance-plan.md; hazard-driven priority elevation; per-taskImplements-directive headers./speckit.v-model.implement/speckit.implementrun-v-model-gate.sh); four-level test generation; sentinel-managed splicing into existing sources;Implements-directive hallucination guard; post-implement trace hook.New hooks:
after_specify→v-model.requirements;before_implement→v-model.trace;after_implement→v-model.trace. Plus eight validator/MF hardenings (status gate, domain profile, schema validator, splicer hardening, etc.).v0.7.1 — Bridge Command Reconciliation & Governance
Reconciles the v0.7.0 bridge commands with their user-facing intent — that
/speckit.v-model.implementproduces a fully working and validated implementation from the V-Model artefact set:implement. No graceful skip on missing test plans or design artefacts; iteratesmodule-design.mddirectly per the V-Model design; explicit test-first emphasis pulling all V-Model artefacts into code-gen context./speckit.v-model.planandtasksclarified as OPTIONAL. The Direct Path via/speckit.v-model.implementis self-sufficient; the optional bridges exist for users mixing V-Model with spec-kit-core's downstream toolchain.AGENTS.md(replaces auto-generatedCLAUDE.md); constitution v1.0.0 → v1.1.0 with additive Bridge Command Discipline, V-Model Artifact Map, and expanded ID schema.No new commands or hooks in v0.7.1.
Verification
python3 -c "import json; json.load(open('extensions/catalog.community.json'))"Full release narratives: