Repository navigation
chore(release): prepare Python 2.0.2 and Rust 2.0.1 - #549
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.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.
Summary
Validation
uv run ruff check prompty testsuv run pytest tests\test_memory.py tests\model\test_vector_conformance.py -quv run --with flit flit build --format wheeluv run --with flit flit build --format sdistcargo check --workspace --lockedcargo package --workspace --locked --allow-dirtygit --no-pager diff --checkRelease notes
After this PR merges, the Rust publish workflow can publish
rust/2.0.1when the PR has therelease: rustlabel. Python publish still requires creating/pushing thepython/2.0.2tag against the merged commit so the source version matches the tag.