Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotfix version parsing breaking build by ignoring non-semver #55

Merged
merged 1 commit into from
Feb 3, 2023

Conversation

hobofan
Copy link
Member

@hobofan hobofan commented Feb 3, 2023

FIXES #54

  • Bump compare-versions to latest version
  • Split out versions that are non-semver compliant before sorting for the time being

@hobofan hobofan requested a review from alexeagle February 3, 2023 08:00
@hobofan hobofan merged commit dadcc83 into bazel-contrib:main Feb 3, 2023
@hobofan hobofan deleted the hotfix_unparsable_versions branch February 3, 2023 15:33
@alexeagle
Copy link
Contributor

@hobofan I think this got the sorting backwards. https://registry.bazel.build/modules/rules_python is suggesting to copy-paste a snippet that gives 0.4.0 while the latest is 0.18.1

@hobofan
Copy link
Member Author

hobofan commented Feb 16, 2023

@alexeagle Ah damn, you are right. When going to the non-versioned page it also picks the oldest version as the latest version. I tried to straighten out the sorting, but looks like I missed that part.

Will open a PR ASAP.

@alexeagle
Copy link
Contributor

Ping on this @hobofan

@seh
Copy link

seh commented Mar 6, 2023

This came up today in the "bzlmod" channel of the "Bazel" Slack workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better support fo module version format
3 participants