spec-kitty-cli 3.2.0a1__tar.gz → 3.2.0a3__tar.gz

{spec_kitty_cli-3.2.0a1 → spec_kitty_cli-3.2.0a3}/CHANGELOG.md

@@ -9,6 +9,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.2.0a3] - 2026-04-21
+
+### Fixed
+
+- Release publish no longer hard-fails when the private `SPEC_KITTY_SAAS_READ_TOKEN` secret is absent. The pipeline still enforces runtime drift and exact wheel installability, and it runs the SaaS consumer-contract check whenever the private compatibility reference can actually be fetched.
+
+## [3.2.0a2] - 2026-04-21
+
+### Changed
+
+- `spec-kitty-runtime` is now pinned to `0.4.4`, matching the corrected published runtime line rather than the broken `0.4.3` metadata.
+- Release readiness and tag-time publish pipelines now verify shared-package drift, candidate-wheel installability with plain `pip`, and candidate compatibility against the SaaS consumer contract before publish.
+
+### Removed
+
+- Temporary `tool.uv.override-dependencies` masking for `spec-kitty-events`. Release validation now requires the published runtime metadata to resolve cleanly without local overrides.
+
 ## [3.2.0a1] - 2026-04-20
 
 ### Added

{spec_kitty_cli-3.2.0a1 → spec_kitty_cli-3.2.0a3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 3.2.0a1
+Version: 3.2.0a3
 Summary: Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation.
 Project-URL: Repository, https://github.com/Priivacy-ai/spec-kitty
 Project-URL: Issues, https://github.com/Priivacy-ai/spec-kitty/issues
@@ -66,7 +66,7 @@ Requires-Dist: requests>=2.33.0
 Requires-Dist: rich>=14.3.3
 Requires-Dist: ruamel-yaml>=0.18.0
 Requires-Dist: spec-kitty-events==3.2.0
-Requires-Dist: spec-kitty-runtime==0.4.3
+Requires-Dist: spec-kitty-runtime==0.4.4
 Requires-Dist: spec-kitty-tracker==0.4.2
 Requires-Dist: toml>=0.10.2
 Requires-Dist: transitions>=0.9.2

{spec_kitty_cli-3.2.0a1 → spec_kitty_cli-3.2.0a3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "3.2.0a1"
+version = "3.2.0a3"
 description = "Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation."
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -62,7 +62,7 @@ dependencies = [
     "packaging>=23.0",
     "psutil>=5.9.0",  # Cross-platform process management for dashboard
     "spec-kitty-events==3.2.0",
-    "spec-kitty-runtime==0.4.3",
+    "spec-kitty-runtime==0.4.4",
     "spec-kitty-tracker==0.4.2",
     "websockets>=12.0",  # WebSocket client for sync protocol
     "toml>=0.10.2",  # Config file parsing
@@ -403,13 +403,3 @@ do_not_mutate = [
     "src/specify_cli/upgrade/migrations/",
     "src/specify_cli/version_utils.py",
 ]
-
-[tool.uv]
-# Override spec-kitty-runtime's transitive pin on spec-kitty-events==2.9.0.
-# runtime 0.4.2 imports from spec_kitty_events.mission_next which exists in
-# the current contract-bearing events release line. This remains an upstream
-# packaging bug in spec-kitty-runtime
-# (tracked: Priivacy-ai/spec-kitty-runtime#TBD).
-override-dependencies = [
-    "spec-kitty-events==3.2.0",
-]

{spec_kitty_cli-3.2.0a1 → spec_kitty_cli-3.2.0a3}/scripts/release/README.md

@@ -54,6 +54,39 @@ Extracts a version section from `CHANGELOG.md` for GitHub Release notes.
 python scripts/release/extract_changelog.py 2.0.0
 ```
 
+### `check_shared_package_drift.py`
+
+Validates that the CLI, SaaS app, and published runtime source agree on the
+current contract-bearing package pins and that no emergency `tool.uv`
+override remains in the CLI metadata.
+
+```bash
+python scripts/release/check_shared_package_drift.py \
+  --saas-pyproject ../spec-kitty-saas/pyproject.toml \
+  --runtime-pyproject /path/to/spec-kitty-runtime/pyproject.toml
+```
+
+### `check_exact_install.py`
+
+Builds a clean temporary virtualenv and installs the built wheel with plain
+`pip` so release-time dependency metadata is exercised exactly as users will
+see it from PyPI.
+
+```bash
+python scripts/release/check_exact_install.py --package spec-kitty-cli
+```
+
+### `check_candidate_consumer_compat.py`
+
+Validates the built wheel's `Requires-Dist` metadata against the SaaS consumer
+contract document.
+
+```bash
+python scripts/release/check_candidate_consumer_compat.py \
+  --package spec-kitty-cli \
+  --consumer-contract ../spec-kitty-saas/contracts/consumer-compatibility.json
+```
+
 ## Workflow Integration
 
 - PR checks: `.github/workflows/release-readiness.yml`
@@ -63,9 +96,12 @@ Release workflow sequence:
 
 1. run tests
 2. validate release metadata
-3. build and verify artifacts
-4. extract changelog notes
-5. create GitHub Release
+3. build the wheel candidate
+4. verify shared-package drift
+5. verify exact installability from the built wheel
+6. verify candidate compatibility against the SaaS consumer contract
+7. verify artifacts and extract changelog notes
+8. create GitHub Release
 
 ## Local Release Workflow
 
@@ -77,7 +113,14 @@ vim CHANGELOG.md     # add ## [3.1.0a0] - YYYY-MM-DD (or final ## [3.1.0])
 # 2) validate
 python scripts/release/validate_release.py --mode branch --tag-pattern "v*.*.*"
 python -m pytest
+python scripts/release/check_shared_package_drift.py \
+  --saas-pyproject ../spec-kitty-saas/pyproject.toml \
+  --runtime-pyproject /path/to/spec-kitty-runtime/pyproject.toml
 python -m build
+python scripts/release/check_exact_install.py --package spec-kitty-cli
+python scripts/release/check_candidate_consumer_compat.py \
+  --package spec-kitty-cli \
+  --consumer-contract ../spec-kitty-saas/contracts/consumer-compatibility.json
 twine check dist/*
 
 # 3) clean build artifacts
@@ -132,6 +175,11 @@ python -m pip install --upgrade --pre spec-kitty-cli
 python -m pip install --upgrade "spec-kitty-cli==3.1.0a0"
 ```
 
+If exact install fails locally but the repo still resolves under `uv`, stop and
+fix the published dependency metadata first. Do not reintroduce
+`tool.uv.override-dependencies` for `spec-kitty-*` packages as a release
+workaround.
+
 ## Testing
 
 ```bash