Skip to content

Latest commit

 

History

History
84 lines (56 loc) · 3.25 KB

CHANGELOG.md

File metadata and controls

84 lines (56 loc) · 3.25 KB

Changelog — SpecJudge for spec-kit

Versioned in lockstep with SpecJudge from 0.5.4 onward. It used to have its own numbers (0.1.x), which said something useful — the extension is a manifest and a prompt and changes far less often than the tool it wraps — but the community catalog pins a single download URL and validates that the declared version matches the release tag it points at. Keeping an independent number would mean a release tag of its own for every change. One number for the whole repository is the cheaper answer, and the cost is that this one moves when SpecJudge moves even if nothing here changed.

[0.7.1] - 2026-11-04

Changed

  • Nothing here moved. The number follows SpecJudge, which fixed a field the CLI reported empty and re-verified its catalog prices.

[0.7.0] - 2026-09-24

Changed

  • Nothing here moved. The number follows SpecJudge, whose judge can now be any OpenAI-compatible endpoint. The extension shells out to the tool, so it inherits whatever judge the user has configured without a manifest change.

[0.6.1] - 2026-09-22

Changed

  • Nothing here moved. The number follows SpecJudge, which fixed a budget defect in how much of each context file reaches the judge.

[0.6.0] - 2026-09-22

Changed

  • Nothing here moved. The number follows SpecJudge, which learned to read Copilot's path-specific instructions — the extension passes the project through unchanged, so it picks up the new source without a manifest change.

[0.5.5] - 2026-09-04

Added

  • The README explains "discovery only — not installable", which is what spec-kit says next to every third-party extension until a project approves the community catalog. Someone who finds this by searching reads that beside our name and reasonably concludes the fault is ours; it is not, and the command to change it is now written down — along with the part that command does not say out loud, that it approves the whole catalog rather than one extension.

[0.5.4] - 2026-08-12

Changed

  • Versioned with SpecJudge from here on (see above). No change to the manifest, the command or the hook: 0.5.4 is 0.1.2 with a number the catalog can validate.

[0.1.2] - 2026-08-12

Fixed

  • The install command in this README was wrong. --from supplies the source, it does not replace the name, so the line published with 0.1.1 fails on the first try. The archive is republished under a new version rather than replaced in place: two different zips answering to 0.1.1 is worse than a version number spent on a one-line fix.

[0.1.1] - 2026-08-12

Fixed

  • The extension would not install on spec-kit 0.14 or newer. The manifest pinned >=0.13.0,<0.14.0, so a compatible extension was refused over an upper bound that was a guess rather than a finding. It now declares a floor and no ceiling, and the README says which versions were actually tested. Verified installing on 0.15.2.

[0.1.0] - 2026-08-12

Added

  • speckit.specjudge.recommend — runs SpecJudge over the current project and reports the podium, the budget envelope and the fragment behind each level.
  • An optional after_tasks hook, so the recommendation arrives at the one moment it is both informed and free: the tasks exist, nothing has been implemented.