fix: version.local field can be none! - #2271
Merged
casperdcl merged 1 commit intoJan 28, 2026
Merged
Conversation
Co-authored-by: Casper da Costa-Luis <[email protected]>
casperdcl
force-pushed
the
fix-version-local-can-be-none
branch
from
January 28, 2026 17:33
7ce4282 to
a500f7a
Compare
casperdcl
self-requested a review
January 30, 2026 13:41
casperdcl
removed their request for review
January 30, 2026 13:41
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.
Despite best efforts, the version.py change can still be broken in some settings. This should fix that.
The current setup is not conducive to local testing for things like this, so it snuck through in one of the polishing commits on #2269