You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waiting for the patch stream to settle — this candidate needs to be observed unchanged for 1 consecutive daily check(s) before an upgrade is prepared (no fixed calendar window; FR-002).
Evaluated the upgrade path: needs a migration beyond a version bump — routed to a maintainer
wing-commander vendors Spec Kit's setup-plan.sh rather than calling an installed package, and its current version emits --json output with a SPECS_DIR key (.specify/scripts/bash/setup-plan.sh:73-78, confirmed by reading the file). Upstream v1.0.5's changelog includes "fix(scripts): name setup-plan's feature directory key FEATURE_DIR (#4397)" — a rename of that same JSON key. This repo has at least two direct consumers hard-coded to the old SPECS_DIR key name: (1) the speckit-plan skill instructions at .claude/skills/speckit-plan/SKILL.md:60, which tell the agent to "parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH", and (2) the auto-update-spec-kit.yml workflow's self-test at line 2276, which extracts .SPECS_DIR from setup-plan.sh's output and fails the gate if it's absent (line 2278-2280, with the failure detail explicitly naming SPECS_DIR as the "documented" shape). Simply bumping the pinned version string and pulling in upstream's renamed script would silently break the auto-update gate and misalign the skill's documented contract with the actual output — this requires updating the vendored script's JSON key together with its downstream consumers, not a plain version bump. Per instructions, no partial/best-effort migration is proposed here; this should route to a human to perform the coordinated rename.
Activity
wing-commander-bot commentedon Sep 10, 2026
Evaluated the upgrade path: needs a migration beyond a version bump — routed to a maintainer
wing-commander vendors Spec Kit's setup-plan.sh rather than calling an installed package, and its current version emits
--jsonoutput with aSPECS_DIRkey (.specify/scripts/bash/setup-plan.sh:73-78, confirmed by reading the file). Upstream v1.0.5's changelog includes "fix(scripts): name setup-plan's feature directory key FEATURE_DIR (#4397)" — a rename of that same JSON key. This repo has at least two direct consumers hard-coded to the oldSPECS_DIRkey name: (1) the speckit-plan skill instructions at .claude/skills/speckit-plan/SKILL.md:60, which tell the agent to "parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH", and (2) the auto-update-spec-kit.yml workflow's self-test at line 2276, which extracts.SPECS_DIRfrom setup-plan.sh's output and fails the gate if it's absent (line 2278-2280, with the failure detail explicitly naming SPECS_DIR as the "documented" shape). Simply bumping the pinned version string and pulling in upstream's renamed script would silently break the auto-update gate and misalign the skill's documented contract with the actual output — this requires updating the vendored script's JSON key together with its downstream consumers, not a plain version bump. Per instructions, no partial/best-effort migration is proposed here; this should route to a human to perform the coordinated rename.Sources:
No changes were applied — this upgrade needs more than a version bump, so a maintainer needs to perform the migration by hand.
wing-commander-bot commentedon Sep 11, 2026
A newer candidate (v1.0.6) superseded the previously-watched v1.0.5 before it settled — restarting the settle count at 1.