search

bazel-contrib / bcr-ui

Website for the Bazel Central Registry
https://registry.bazel.build
Apache License 2.0
14 stars 9 forks source link

Issue with package version sorting when `.bcr.*` versions are involved #142

Open redsun82 opened 4 months ago

redsun82 commented 4 months ago

I've noticed that for the zstd and the google test packages there are .bcr.1 packages that even though are more recent than the latest version and they presumably fix issues with the bazel central registry patching, they are not shown up as the latest versions nor appear in the correct order in the all versions list.

This has caused a problem specifically with zstd, as the .bcr.1 version contains this fix without which we could not use that dependency, and it was not at all clear from the start we needed to get that version.

hobofan commented 4 months ago

Thanks for bringing this up! At the core this sounds like what has already been discussed in https://github.com/bazel-contrib/bcr-ui/issues/54 (and https://github.com/bazel-contrib/bcr-ui/issues/22).

The efforts on that front have become a bit stale on my front, but I'll try to push it forward soon (it's essentially fixed on a technical level, but need to go through some organizational motions so that I don't end up as the single point of failure here).

lalten commented 3 months ago

Why does the BCR UI even re-sort the versions? Wouldn't it be enough to go with the order of the version list in metadata.json? (https://github.com/bazel-contrib/bcr-ui/issues/54#issuecomment-1416286960)