tree 07fa890eaa195e3b9935aef0f4792aeda5860066
parent 52c640737d32c709e8219c2607918ca7e780b485
author Jan Schär <jan@jschaer.ch> 1712590425 +0200
committer Jan Schär <jan@jschaer.ch> 1712657832 +0000

build/status: fix version sorting

The removed comment claimed that version strings can be sorted 
lexicographically, but that only works as long as all parts of the 
version are less than 10.

Instead, use the version-aware sorting of git-tag.

Manual testing steps:

git tag metropolis-v0.3.0
git tag metropolis-v0.21.0
git tag metropolis-v0.22.0
./build/print-workspace-status.py
# Expected output contains: metropolis_version v0.22.0
# Cleanup:
git tag -d metropolis-v0.3.0 metropolis-v0.21.0 metropolis-v0.22.0

Change-Id: I7f0f989845e4d9f940bf01bd2cc6a535b4d4a589
Reviewed-on: https://review.monogon.dev/c/monogon/+/2922
Vouch-Run-CI: Serge Bazanski <serge@monogon.tech>
Tested-by: Jenkins CI
Reviewed-by: Serge Bazanski <serge@monogon.tech>