Repository navigation
chore(release): 1.4.0 - #47
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <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
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.
What this changes
Release commit for evalshift CLI 1.4.0 (minor). It bumps the
pyproject.toml, DOCS.md and llms-full.txt version lines. It also renames the CHANGELOG's[Unreleased]section to[1.4.0] - 2026-10-11and opens a fresh[Unreleased]above it.Why
Ships everything merged since 1.3.0:
capture sync/promoteread every wrapped provider's native message shape, and newcapture sync --repairrebuilds cases an earlier sync stringified or emptied.initscaffoldssemanticfor every provider, and judge/embedding API keys are checked before the first call. An advisory evaluator without a key is skipped; a blocking one exits 1.doctorgains anevaluator keysrow.doctor'scaptures.storerow warns instead of failing when the store library is missing. That failure was turningcompareand Action runs red. Messages now name the package to install.Why 1.4.0 and not the 1.3.1 in the sink plan: #45 and #46 add features. #45 also changes behaviour for existing CI: a
semantic/llm_judgegate whose model has no API key now exits 1 before any call. It used to land oninconclusiveand pass--policy-gate. The CHANGELOGChangedsection calls this out. A minor bump matches how 1.2.0 shipped theslices:removal.Pairs with evalshift-sdk 0.6.0 (evalshift/evalshift-sdk#16). The docs say "SDK 0.6.0+, or
EVALSHIFT_SINKon 0.5.0", so the two are independent and theevalshift-sdk>=0.4.0floor is unchanged.After merge: tag
v1.4.0on the merge commit, which makes release.yml publish to PyPI. The action'sbump-cli-pinworkflow then opens the pin PR.Test plan
make ci(ruff check, format check, mypy --strict,pytest --cov-fail-under=90): 2994 passed, coverage 94.91%evalshift --versionis 1.4.0 after reinstall🤖 Generated with Claude Code