Repository navigation
chore: bump version to 1.7.0 - #265
Merged
Merged
Conversation
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.
The version on main (1.2.0) maps to a tag that already belongs to an earlier release, so the Pydantic 2 upgrade cannot be tagged with that version.
Bump the release to 1.7.0, the next minor version after the highest existing release tag, v1.6.1. Keep config.json, pyproject.toml, and the project entry in uv.lock consistent. Dependency versions are unchanged.
Validation: JSON/TOML version consistency, uv lock --check --offline, poetry check, and git diff --check passed. Application tests were not run because this changes release metadata only.