)]}'
{
  "commit": "db3866a782c443baf4eac4e1cf2b7d03b1bf6c5e",
  "tree": "07fa890eaa195e3b9935aef0f4792aeda5860066",
  "parents": [
    "52c640737d32c709e8219c2607918ca7e780b485"
  ],
  "author": {
    "name": "Jan Schär",
    "email": "jan@jschaer.ch",
    "time": "Mon Apr 08 17:33:45 2024 +0200"
  },
  "committer": {
    "name": "Jan Schär",
    "email": "jan@jschaer.ch",
    "time": "Tue Apr 09 10:17:12 2024 +0000"
  },
  "message": "build/status: fix version sorting\n\nThe removed comment claimed that version strings can be sorted \nlexicographically, but that only works as long as all parts of the \nversion are less than 10.\n\nInstead, use the version-aware sorting of git-tag.\n\nManual testing steps:\n\ngit tag metropolis-v0.3.0\ngit tag metropolis-v0.21.0\ngit tag metropolis-v0.22.0\n./build/print-workspace-status.py\n# Expected output contains: metropolis_version v0.22.0\n# Cleanup:\ngit tag -d metropolis-v0.3.0 metropolis-v0.21.0 metropolis-v0.22.0\n\nChange-Id: I7f0f989845e4d9f940bf01bd2cc6a535b4d4a589\nReviewed-on: https://review.monogon.dev/c/monogon/+/2922\nVouch-Run-CI: Serge Bazanski \u003cserge@monogon.tech\u003e\nTested-by: Jenkins CI\nReviewed-by: Serge Bazanski \u003cserge@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af6207972d4a8059988da58fc6d0083af7f0c1fc",
      "old_mode": 33261,
      "old_path": "build/print-workspace-status.py",
      "new_id": "28387302d3d99fbf9ffa5af7b4641323ba6e349b",
      "new_mode": 33261,
      "new_path": "build/print-workspace-status.py"
    }
  ]
}