Bump version to 2.0.10#66
Open
leoromanovsky wants to merge 2 commits into
Open
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.
Motivation
The latest published release is 2.0.9, but main now includes several merged changes that are not in a PyPI patch release. Preparing a 2.0.10 patch release gives users a clear version that includes the SQLAlchemy behavior fixes, while also documenting the CI and release-infrastructure changes that landed after 2.0.9.
Changes
This bumps the package version in pyproject.toml from 2.0.9 to 2.0.10 and adds 2.0.10 changelog entries for every merged PR on main since v2.0.9:
Decisions
This PR keeps the scope to release metadata only. It does not restore the removed publish workflows from #57; after merge, maintainers should use the current publishing process to publish the 2.0.10 artifact.