)]}'
{
  "commit": "581f83dcdbbbe827ca8eda20b85ec869b8be1e99",
  "tree": "d8fba820b195b89c722cea193e6c5256ffac6536",
  "parents": [
    "d9ad235cd8c203db7430c366751f1dddcf450060"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue Sep 10 19:04:36 2024 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Sep 13 22:52:17 2024 +0000"
  },
  "message": "Prepare to tag 0.20240913.0 as the first periodic snapshot\n\nBoringSSL is a \"live at head\" project and does not make release\nbranches and thus releases.\n\nHowever, some systems cannot consume git revisions and expect git tags.\nIn Bazel Central Registry\u0027s case, the toolchain is suspicious of\nnon-\"release\" archives of\nhttps://github.blog/open-source/git/update-on-the-future-stability-of-source-code-archives-and-hashes/\n\nTo accommodate such systems, let\u0027s start periodically tagging snapshots\nas \"releases\". These versions do not represent any kind of stability or\ndevelopment milestone.  BoringSSL does not branch at these releases and\nwill not cherry-pick bugfixes to them. Unless there is a technical\nconstraint to use one of these revisions, projects should simply use the\nlatest revision when updating.\n\nAlso, so that cutting such revisions is less tedious, probably the\nsimplest is to set MODULE.bazel\u0027s version field in HEAD to whatever the\nlast revision was. The process will then be:\n\n1. Bump MODULE.bazel\u0027s version\n2. Create a git tag\n3. Create a GitHub \"release\"\n4. Kick off a BCR update\n\nAll that mess will ideally be automated, but for now we\u0027ll drive that\nmanually. Update INCORPORATING.md to explain these tags, and also to\ndiscuss the new pregenerated build files.\n\nVersioning scheme is chosen as 0.YYYYMMDD.N so that:\n- It is deterministic from the date\n- It begins with zero lest anyone misinterpret these as semver versions\n- We have a digit at the end to bump when we need to cut two revisions\n  in one day\n\nChange-Id: Ie256a5f0f7eaac5928b537c75f82402c934f9fc3\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71227\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "afe61d9ff715216e4a5e03e28f05a17626d7e67f",
      "old_mode": 33188,
      "old_path": "INCORPORATING.md",
      "new_id": "1a4eb476c487f2d5562c43f283c0e18d2d0ebfc0",
      "new_mode": 33188,
      "new_path": "INCORPORATING.md"
    },
    {
      "type": "modify",
      "old_id": "0447733fea27043995580e658bd8d77f3b76e55c",
      "old_mode": 33188,
      "old_path": "MODULE.bazel",
      "new_id": "69a29fc26e6c844f1f41435e91eaa6987f2c7d8f",
      "new_mode": 33188,
      "new_path": "MODULE.bazel"
    }
  ]
}