chore(release): 1.2.0 - #27
Merged
Merged
Conversation
DeepSeek joins the supported providers end to end (registry, tool-call parsing, thinking-mode temperature handling, doctor/init), and repeat runs of agent suites now hit the response cache per tool-call round instead of always going live. The top-level `slices:` key is removed from evalshift.yaml — it was validated and recorded but never read by analysis — plus several doc-accuracy and latency/cache-concurrency fixes. Shipped as a minor despite the breaking `slices` removal, the same way 1.1.0 shipped `thresholds`: the key gated nothing, so a config that never set it needs no migration, and one that did gets a load-time error naming the fix. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 1.2.0.
deepseek-*id resolution,DEEPSEEK_API_KEYpre-check anddoctorrow, tool-call eval parsing, judge-family self-preference warning,evalshift init --provider deepseek, and non-determinism handling for DeepSeek's thinking-mode temperature behavior.evalshift doctor's config row now points atevalshift validatefor details. Repeat runs of agent (tool-calling) suites now hit the response cache per replayed round instead of always running live.slices:key is gone fromevalshift.yaml. It was validated and recorded in the run bundle but never read byanalyze— slices have always come from exampletags— so a config that still sets it now fails to load with an error naming the fix, the same waythresholdswas handled in 1.1.0.evalshiftprocesses, a SQLAlchemy 2.1 in-memory cache concurrency bug, and a DeepSeek pricing lookup miss.Full details in CHANGELOG.md.
After merge
The tag
v1.2.0is pushed after merge, which triggers.github/workflows/release.ymlto publish to PyPI.Test plan
make cigreen (ruff check, ruff format --check, mypy --strict, pytest — 2447 passed, 94.50% coverage)tests/unit/test_docs_currency.pypasses with the bumped version headersuv run evalshift --versionprints1.2.0uv buildsucceeds —evalshift-1.2.0-py3-none-any.whlandevalshift-1.2.0.tar.gz(not uploaded)🤖 Generated with Claude Code