Repository navigation
chore(release): 2.20.0 - #106
Merged
Merged
Conversation
Promotes the Unreleased entries (AssessResponse.more_claims, extract's 100-claim ceiling, the Python 3.10 floor) to a dated 2.20.0 section and leaves a fresh empty Unreleased header. No source or openapi.json change needed: pyproject.toml's version stays git-tag-derived via hatch-vcs (by design, per its own comment: "never have to hand-bump pyproject.toml"), and openapi.json is already byte-identical to a fresh emit from the Lenz API (confirmed by diff against a fresh `manage.py emit_openapi` run), so the /assess "20 a call" copy-only change needed no resync. Verified locally the way CI does: ruff check + format, mypy --strict, pytest (full suite, 92.41% coverage vs. 87% floor), wheel build. 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
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.
What changes
Promotes the
CHANGELOG.md[Unreleased]section to a dated[2.20.0] - 2026-10-05section (AssessResponse.more_claims,extract's 100-claim ceiling, the Python 3.10 floor) and leaves a fresh empty[Unreleased]header above it. Nothing else.pyproject.toml's version is git-tag-derived viahatch-vcsby design — its own comment says "Source the version from the git tag at build time so we never have to hand-bump pyproject.toml." There is nothing to bump here; 2.20.0 takes effect only when a maintainer pushes thev2.20.0tag.openapi.jsonchange. Diffed the committedopenapi.jsonagainst a freshmanage.py emit_openapirun from the Lenz repo's currentorigin/main(which already includes the/assess"20 a call" copy fix) — byte-identical, and also byte-identical to the Node SDK's copy. It was already resynced in an earlier PR, so there is nothing to regenerate here.AssessResponse.more_claims/extract(100) to promote, plus its own Node-20.19-floor entry, so both SDKs stay in lockstep.Verified locally, the way CI does
uv sync --all-extrasruff check .— all checks passedruff format --check .— 40 files already formattedmypy src/lenz_io(strict) — no issuespytest -q(full suite, coverage gate) — 92.36%, floor 87%, all greenuv build --wheel— builds cleanPost-deploy actions and prod testing
None — this PR only reshapes
CHANGELOG.md. Nothing publishes from merging it.Publish steps for after merge (per
.github/workflows/release.ymlandCONTRIBUTING.md): push thev2.20.0tag on the merge commit.hatch-vcsresolves the wheel/sdist version from that tag at build time (nothing to commit beforehand),release.ymlbuilds and publishes to PyPI via OIDC trusted publishing, runs the opt-in staging smoke test, and posts a Discord notification on success. No GitHub Release object is created by the workflow itself.🤖 Generated with Claude Code