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

[bug] Bad latest version #184

Closed
franramirez688 opened this issue Nov 25, 2024 · 4 comments
Closed

[bug] Bad latest version #184

franramirez688 opened this issue Nov 25, 2024 · 4 comments
Assignees

Comments

@franramirez688
Copy link
Contributor

Based on #187

In case of cci.xx.x.x and x.x.x, latest ones should be x.x.x and not the other ones.

For instance:

Screenshot 2024-11-25 at 15 53 42
Screenshot 2024-11-25 at 15 53 35

Here, the latest one should be 0.4.0

@AbrilRBS
Copy link
Member

Note that this is endemic to every cci recipe using the old scheme, Conan will also order this incorrectly

@franramirez688
Copy link
Contributor Author

Note that this is endemic to every cci recipe using the old scheme, Conan will also order this incorrectly

Yes, but we can reorder the versions through the frontend and show the latest ones.

@davidsanfal
Copy link
Contributor

is the idea to always place the cci versions after the standard ones or also taking into account also the x.y.z numbers? I suppose it is by placing the cci last, but just to confirm what is really expected

@AbrilRBS
Copy link
Member

AbrilRBS commented Dec 4, 2024

If it starts with cci, they should show up last yes, as Conan is sorting them "wrong".

But conversely new versions that contain cci (1.2.cci.20240101) can be sorted correctly by Conan so those would need no fix, but is also not s problem if they are sorted last with the other cci ones

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

No branches or pull requests

3 participants