@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.4.0] - 2026-10-11
+
 ### Added
 
 - `capture sync --repair` rebuilds the `inputs` and `history` of cases an
 
@@ -12,7 +12,7 @@ hosted (opt-in)  run history, diffs, PR gates
 
 The suite is the crux, so the capture SDK is the recommended way to build one: it records real production runs to disk and `evalshift capture sync` promotes them into golden suites. Hand-written suites are fully supported — see [The golden suite](#the-golden-suite).
 
-- **Package name:** `evalshift` · **CLI entry point:** `evalshift` · **version:** 1.3.0
+- **Package name:** `evalshift` · **CLI entry point:** `evalshift` · **version:** 1.4.0
 - **Python:** >= 3.11 · **License:** Apache-2.0 · **Status:** stable
 - **Local-first.** Runs, scores, stats, and reports all happen on your machine under `.evalshift/`. The only network calls are the model API calls you asked for — and, if you opt in, pushes to the hosted service and reads from a capture bucket you own (`captures.store`).
 - **Four pieces:** CLI (this doc), SDK, GitHub Action, hosted server — each with its own machine-readable reference for AI tools. See [Ecosystem and AI-tool references](#ecosystem-and-ai-tool-references).
 
@@ -1,7 +1,7 @@
 # evalshift (CLI) — complete reference for AI tools
 
 Canonical hosted copy: https://www.evalshift.dev/cli-llms-full.txt
-Package: evalshift (PyPI) | CLI entry point: evalshift | version: 1.3.0
+Package: evalshift (PyPI) | CLI entry point: evalshift | version: 1.4.0
 Python: >=3.11 | license: Apache-2.0 | status: stable
 Install: pip install evalshift   (or: uv pip install evalshift)
 
 
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "evalshift"
-version = "1.3.0"
+version = "1.4.0"
 description = "Run your prompts on two LLMs and find out, with statistical confidence, what regressed."
 readme = "README.md"
 license = "Apache-2.0"