Repository navigation
Prepare v0.1.0 release - #1
Merged
Merged
Conversation
hotchpotch
marked this pull request as ready for review
September 19, 2026 13:42
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
Prepare v0.1.0, the first release with Jev reranking and relevance filtering, following the scaffolding-only v0.0.1 release. The implementation is already on main; this PR updates the release metadata and includes the latest README wording cleanup.
pyproject.tomlanduv.lockto 0.1.0 without changing dependencies.docs/releases/v0.1.0.md, resetHEAD.md, and update the changelog.Validation
uv sync --locked --devuv run --locked tox: 203 passed, 52 live tests skipped; lint and type checks passed.uv build --no-sources --clear: wheel and source distribution built successfully.uv run --locked twine check --strict dist/*: both distributions passed.python scripts/release-notes.py v0.1.0and checked the diff for whitespace errors.Live API tests were not run for this metadata and documentation change.
Publication
After review and passing CI, merge this PR. Create an annotated
v0.1.0tag on the exact merged commit after its CI passes, then push the tag to start the release workflow. The workflow publishes through PyPI Trusted Publishing and attaches the same distributions to the GitHub Release. This PR does not publish the package by itself.