prefix.dev UI should not show yanked versions as the most recent, regardless of version

[Ahajha]

Issue description

We yanked some mojo package versions due to changing version strategy early on, so we added a 0. in front of the versions.

The UI here shows a yanked version as the latest: https://prefix.dev/channels/max/packages/mojo. This also leads to showing that the channel hasn't been updated in several months here: https://prefix.dev/channels/max

Expected behavior

Instead, 0.26.1.0 should be the latest.

[baszalmstra]

Can you explain how you yanked the package? The UI on prefix.dev also doesnt show that the package is yanked.

[Ahajha]

I yanked it using the REST API, this was ~August of last year and when the yanking API was new. But it does at least work, if we install the latest we get a >1.0 version instead of this 25.5.0.

[baszalmstra]

Can you explain how you do that?

I just tried:

> pixi init --platform linux-64 --channel https://conda.modular.com/max/ --channel https://prefix.dev/conda-forge
> pixi add mojo
✔ Added mojo >=25.5.0,<26

[Ahajha]

Oh... Hmm let me test then

[Ahajha]

Okay that's an issue. Let me try yanking it again and see if that changes anything.

[baszalmstra]

Note that you can just do this through the UI now.

[Ahajha]

Okay two separate issues here, it seems I forgot to yank the packages in the max channel, but I did yank the ones in the max-nightly channel, but the UI issue is still relevant. Going to edit the ticket description.

Also thanks, that's good information, I'll use the UI for this.

[Ahajha]

Actually, since the pixi search issue was on my end, is there somewhere else I should file the UI issue? Or is here fine?

[baszalmstra]

Looping in @tdejager who is working on the frontend.

[tdejager]

Does that mean you want to deprioritize yanked versions in the UI? Because they do have the yanked label.

[Ahajha]

Yea I think they should be moved behind non-yanked versions

[Ahajha]

Also pixi search mojo -c https://conda.modular.com/max/ is still showing 25.5.0 as the latest, but I assume there is some sort of sync that needs to happen (I've already tried clearing all of my caches)

[baszalmstra]

It might take a moment indeed. I think it has propagated now:

❯ pixi search mojo -c https://conda.modular.com/max -p linux-64
Using channels: https://conda.modular.com/max/

mojo-0.26.1.0-release
---------------------

Name                mojo
Version             0.26.1.0
Build               release
Size                89061870
License             LicenseRef-Modular-Proprietary
Subdir              linux-64
File Name           mojo-0.26.1.0-release.conda
URL                 https://conda.modular.com/max/linux-64/mojo-0.26.1.0-release.conda
MD5                 Not available
SHA256              e945e8fbff0fdd2064ea193b26fb4ba95ab782367cfd2a2c4522350066434494

Dependencies:
 - python >=3.10
 - mojo-compiler ==0.26.1.0 release
 - mblack ==26.1.0 release
 - jupyter_client >=8.6.2,<8.7

Run exports:

Other Versions (3):
Version   Build
0.25.7.0  release
0.25.6.1  release
0.25.6.0  release