)]}'
{
  "commit": "0b9276519a7475c3a341f78d83ca8d18cec3b38a",
  "tree": "4824ee5afec87621b60d6cf06e22d3c696d3a978",
  "parents": [
    "a3e38cf9a4fcc0940402c4f18172662a84e28151"
  ],
  "author": {
    "name": "Jan Schär",
    "email": "jan@monogon.tech",
    "time": "Wed Jul 31 18:08:50 2024 +0200"
  },
  "committer": {
    "name": "Jan Schär",
    "email": "jan@monogon.tech",
    "time": "Mon Aug 05 07:36:08 2024 +0000"
  },
  "message": "m/test/launch: consistently use 0-based node indices\n\nPreviously, the first node was sometimes called node 1 in the logs, and \nsometimes node 0. Now it is always called node 0.\n\nOnce all nodes are up, node info is now printed in the order of node \nnumbers. Previously this was random as this was iterating over a map \n(cluster.Nodes).\n\nChange-Id: I0757c89951d7292f2f720237604a3554af4bf404\nReviewed-on: https://review.monogon.dev/c/monogon/+/3293\nTested-by: Jenkins CI\nReviewed-by: Serge Bazanski \u003cserge@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7ae5f83536717697deeaeebd4278be1ae4e5ee9a",
      "old_mode": 33188,
      "old_path": "metropolis/test/launch/cluster.go",
      "new_id": "ac8a0173a8e3e4d071e7a69f9903d29e0782fb20",
      "new_mode": 33188,
      "new_path": "metropolis/test/launch/cluster.go"
    }
  ]
}