chore(release): 0.3.0 - #257
Merged
Merged
Conversation
A minor bump rather than a patch, for two reasons that are not bookkeeping. `--record` is now the default on the six verbs that call a provider, so a run that reaches a model writes a cassette where it previously wrote nothing. `--no-record` declines. A behaviour a person did not ask for and now gets is a minor bump whatever the diff size says, and `init`'s disclosure states it at the moment somebody opts in. And `py.typed` ships, which is a capability the distribution did not have: an adopter's own `lockstep.py` type-checks against the installed package instead of answering `import-untyped` to every framework import. The reason to cut this now rather than at a rounder moment: #226 stops a model reading `.env` through `search_text`, and `git tag --contains 930ab3a` is empty. The fix has been on main and in no installable artifact, while README.md:8 tells a new adopter to install the version that still has the hole. Twenty-nine commits is too many to have gone unreleased and this is the one that made it urgent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Merged
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.
Bumps
pyproject.tomland__version__to 0.3.0. Nothing else changes.Why minor, not patch
Two things in the 29 unreleased commits are not patches:
--recordis now the default on the six verbs that call a provider. A run that reaches a model writes a cassette where it previously wrote nothing;--no-recorddeclines. A behaviour a person did not ask for and now gets is a minor bump whatever the diff size says.py.typedships. That is a capability the distribution did not have — an adopter's ownlockstep.pynow type-checks against the installed package instead of answeringimport-untypedto every framework import.Why now
git tag --contains 930ab3ais empty. #226 — which stops a model reading.envthroughsearch_text— has been on main and in no installable artifact, whileREADME.md:8tells a new adopter to install the version that still has the hole. That is the fact that made this urgent rather than tidy.What ships
29 commits: 13
feat, 14fix, 2docs. The headline set —fix(tools)search_texthad no guard at allfix(redact)feat(packaging)py.typed, and everythinginitwrites survivesmypy --strictfeat(record)implementandfixcan record at allfeat(record)feat(review)/review <lens>from a comment, resolved against the lenses that existfeat(evidence)A fresh
initwill pinin-lockstep[anthropic]==0.3.0, whichtest_gitlab.py:509asserts.make check2120 passed / 4 skipped.After this merges, pushing
v0.3.0publishes to PyPI — the release workflow refuses if the tag and either version disagree.