fix(version): semver version ordering #293
Labels
Clear labels
bug
build
ci/cd
critical fix
design
documentation
duplicate
easy-first-issue
enhancement
help wanted
i10n
i18n
installer
invalid
question
release
release-candidate
security
tech-debt
test
wontfix
Something is not working
go build related issues
Building things with CI/CD
https://docs.coopcloud.tech/federation/resolutions/passed/010/
UI/UX
Documenting all the things
This issue or pull request already exists
Something for new people to get stuck into. We hope it's easy!
New feature
Need some help
Everything to do with localisation
Everything to do with internationalisation
Everything to do with the install script.
Something is wrong
More information is needed
Release management
Related to the new release candidate
Security related
Unit/integration testing
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
moritz
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#293
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Solves coop-cloud/organising#427
This fix sorts the recipe versions at the catalogue generation. This way also old abra clients will work correctly after a regeneration of the catalogue. The fix also sorts the versions that are received from the catalogue, so the catalogue entry order is agnostic to the version order, avoiding any implicit implementation assumptions.
Awesome, thanks for picking this up! Question: can we re-use
tagcmpfor the version comparison operations? I'd like to avoid an additional dependecy if possible.354389839ctoc94cc9d38eI replaced semver with tagcmp. But now I've seen that semver is pulled as indirect dependency anyway. I'm not sure which variant is better.
Aha @moritz righhhht, I forgot 😬 Yeh I'm happy with this as other places in the codebase uses
tagcmp, so it's probably handy to keep using the same API surface. Merge away imho, thanks!