Do not remove invalid software versions #2166
Merged
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.
Added a bit of logic to clean up version strings, and also catch exceptions coming from
packaging.version.parse
:The regex in this PR normalises
0.9.0 (build 0cea70d)
to0.9.0
, fixing the issue.But - honestly, I'm not really sure if we want to do this.
Why do we have to validate that version strings look like version strings? Can we not just accept any string?
Comments like this make me think that the code did that at some point:
However, as far as I see it, if the version string isn't classic semver / recognised format, it's entirely excluded from the report:
Worse - not just that version string, but all versions within that file.
Tagging @vladsavelyev @pontushojer