Skip to content

chore(release): 1.2.0 #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
babaliauskas merged 1 commit into from
Oct 1, 2026
+14 −3
Merged

chore(release): 1.2.0 #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [1.2.0] - 2026-10-01

Shipped as a minor again. The `slices` removal below is breaking by the
letter of SemVer — a config that still sets the key stops loading — but the
field never had any effect: `analyze` has always built one slice per
distinct example tag plus `all`, so `name`, `filter` and `applies_to` renamed,
filtered or scoped nothing. A major would announce a migration that, for
anyone who never wrote `slices:`, does not exist; those who did get a
load-time error naming the key and the fix, the same way `thresholds` was
handled in 1.1.0.

### Added

- DeepSeek is a supported provider. `deepseek-flash` and `deepseek-v4-pro`
Expand Down
2 changes: 1 addition & 1 deletion DOCS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0
- **Package name:** `evalshift` · **CLI entry point:** `evalshift` · **version:** 1.2.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.
- **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).
Expand Down
2 changes: 1 addition & 1 deletion llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.1.0
Package: evalshift (PyPI) | CLI entry point: evalshift | version: 1.2.0
Python: >=3.11 | license: Apache-2.0 | status: stable
Install: pip install evalshift (or: uv pip install evalshift)

Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "hatchling.build"

[project]
name = "evalshift"
version = "1.1.0"
version = "1.2.0"
description = "Run your prompts on two LLMs and find out, with statistical confidence, what regressed."
readme = "README.md"
license = "Apache-2.0"
Expand Down
Loading