Release 2.0.1 and refresh discovery metadata - #61
Merged
Conversation
Maksim-Burtsev
marked this pull request as ready for review
August 2, 2026 17:22
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.
What changed
2.0.12.0.0Why
The published PyPI metadata predates the hosted documentation and typed-package marker, while the GitHub repository still uses a generic discovery description and default social card. This patch prepares a consistent
2.0.1release without changing CLI or migration behavior.Validation
uv lock --checkmake lintmake docsuv builduv run --with twine twine check dist/*migrator --versionreports2.0.1