Correct build issues caused by vcs_versioning==2.0#779
Merged
Conversation
mhsmith
approved these changes
Jun 23, 2026
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
2 participants
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.
Over the last 24 hours, vsc_versioning 2.0 has been released; this has caused problems with scm_versioning.
There's an underlying bug (pypa/setuptools-scm#1434). Based on the recommendation from the maintainers on that ticket, this simplifies version handling to always use importlib metadata.
The direct call to get_version() may have been needed historically because importlib.metadata hadn't been fully formalized, but it isn't any more. The only consequence I can see is that an editable install won't necessarily show the current VCS version.
Also includes some tweaks to the docs configuration that are shared with other projects (disabling a MkDocs 2 warning, and moving the link checker out of the linting task)
PR Checklist: