)]}'
{
  "log": [
    {
      "commit": "8999faafd3184dbc4ba345f72812b29602c5412d",
      "tree": "04be915879bb49de08e4555d7424180052d64cd8",
      "parents": [
        "417d7f6b2e4bbf979ec336cf1dd5eb7599e6535c"
      ],
      "author": {
        "name": "Serge Bazanski",
        "email": "serge@monogon.tech",
        "time": "Mon Nov 20 12:42:13 2023 +0100"
      },
      "committer": {
        "name": "Serge Bazanski",
        "email": "serge@monogon.tech",
        "time": "Thu Dec 21 14:46:59 2023 +0000"
      },
      "message": "version: implement Go tooling\n\nThese two packages implement respectively:\n\n1. A companion Go library to access data from //version/spec\n   Protobuf data.\n2. A Go code generator and related Bazel build infrastructure to convert\n   Bazel build status data into an embedded //version/spec Protobuf\n   Version message.\n\nThe two allow for stamping Go artifacts with a generated spec.Version\nproto, and allows Go code to work with said messages.\n\nThe two systems are split to allow decoupling stamping build artifacts\nfrom processing such version messages. This is so that eg. a Metropolis\nclient tool can receive a server\u0027s Version field, and then show that\nfield to the user.\n\nChange-Id: I82fbfa6bc2418edc979cdc6e1fdee60ee75a88b7\nReviewed-on: https://review.monogon.dev/c/monogon/+/2332\nReviewed-by: Lorenz Brun \u003clorenz@monogon.tech\u003e\nTested-by: Jenkins CI\n"
    }
  ]
}