v2.0.4

🐛 Fixed

• Upgrade JSON machine-parseability hardening (#254): spec-kitty upgrade --json now emits raw JSON output without Rich console wrapping.
• Upgrade migration status consistency (#256): non-applicable migrations are reported as skipped instead of incorrectly marked as applied.

🔧 Changed

• Contract hardening closeout (#213-#218): merged deterministic branch/runtime contracts, typed artifact-path payloads, merge/preflight JSON enrichment, and banner suppression in agent contexts.
• Codex/Copilot slash-flow reliability (#128): integrated slash-command output stability improvements via deterministic JSON/banners/template alignment.
• Worktree/preflight stability (#226): released preflight and command-contract hardening on the 2.x line for end-to-end spec→implement→review runs.

v1.0.3

🐛 Fixed

• Upgrade JSON machine-parseability hardening (#254): spec-kitty upgrade --json now emits raw JSON output without Rich console wrapping side effects.
• Upgrade migration status consistency (#256): non-applicable migrations are now reported as skipped instead of being incorrectly listed as applied.
• Template schema readiness gate: software-dev specify template now contains an explicit meta.json schema block including "target_branch" and "vcs" keys.

🔧 Changed

• Contract hardening closeout (#213-#218): promoted deterministic branch/runtime JSON contracts, safer merge/preflight JSON envelopes, and stricter banner suppression in agent contexts.

v2.0.3

Bug Fixes

• fix: parse both **Requirements** and **Requirement Refs** in tasks.md — The regex in _parse_requirement_refs_from_tasks_md() only matched Requirement Refs but LLM-generated tasks.md files frequently use Requirements instead. The updated pattern accepts both formats, fixing the "Requirement mapping validation failed" error during finalize-tasks. (Fixes #243)

Upgrade

pip install --upgrade git+https://github.com/Priivacy-ai/spec-kitty.git@v2.0.3

v1.0.2

🔧 Changed

• MIT-cleared dependency pin for 1.x CLI: replaced prerelease spec-kitty-events==0.4.0a0 with stable spec-kitty-events==0.4.1.
• Release train compatibility matrix update: recorded explicit train entries for spec-kitty-events, spec-kitty-runtime, and spec-kitty-tracker to keep future releases aligned to MIT-cleared PyPI packages.

v2.0.2

✅ Added

• Flag-gated tracker command group: added spec-kitty tracker ... commands behind SPEC_KITTY_ENABLE_SAAS_SYNC, including provider listing, bind/unbind, mapping, local sync pull/push/run, and snapshot publish.
• Tracker host-local persistence + credentials support: added CLI-owned tracker SQLite cache/checkpoints and provider credential handling consistent with existing Spec Kitty host persistence patterns.

🔧 Changed

• Dependency floor hardening for 2.x installs: added explicit lower bounds for previously unbounded core CLI direct dependencies to reduce resolver drift in fresh environments.
• Workflow review lane guard: review start now requires a valid for_review lane state before progressing.

v1.0.1

🔧 Changed

• Dependency floor hardening for PyPI installs: added explicit lower bounds for previously unbounded core CLI dependencies (typer, rich, httpx[socks], platformdirs, readchar) to reduce resolver drift across clean environments.
• Release validation robustness: release-readiness validation now remains scoped to valid version tags for the active major stream and supports a/b/rc tag parity checks.

v2.0.1

Fixed

• Main bias fix: resolve_primary_branch() now checks the current branch before the hardcoded [main, master, develop] list. Repos on non-standard primary branches (e.g., 2.x) no longer get blocked by spec-kitty specify.
• create_feature() records the current branch as target_branch in meta.json instead of guessing via heuristics. Added --target-branch CLI option for explicit override.
• guards.py uses resolve_primary_branch() instead of hardcoded {"main", "master"} set.
• merge-feature --target auto-detects from meta.json when not specified.
• Template references to "main" replaced with "target branch" throughout command templates.

Changed

• Dashboard --open flag: Browser auto-open is now disabled by default. Pass --open to open the dashboard URL in your browser.
• Consolidated 3 ad-hoc branch-check functions into _show_branch_context().

Install from GitHub

pip install "spec-kitty-cli @ git+https://github.com/Priivacy-ai/spec-kitty.git@v2.0.1"

Spec Kitty CLI v2.0.0 (2.x Companion)

Companion release from branch 2.x in the dual-release model.

• Package version: 2.0.0
• Source branch: 2.x
• Intended use: semantic continuation of the 2.x line, published alongside v1.0.0a1.

This tag pins the current 2.x baseline for downstream consumers.

v1.0.0

🔧 Changed

• Promoted the 1.x line to stable: 1.0.0 supersedes 0.16.2 as the default recommended PyPI install.
• Release lane policy hardened: main continues to publish the 1.x PyPI stream while 2.x remains GitHub-release-only.

Spec Kitty CLI v1.0.0a1 (Alpha RC)

Alpha release candidate from branch main (PyPI publish line).

• Package version: 1.0.0a1
• Source branch: main
• Intended use: alpha/RC validation before stable 1.x

This release is paired with v2.0.0 from branch 2.x as part of the dual-release model.