)]}'
{
  "commit": "1cb4f8fa979ea7582f6937025a9a43f143acb2ae",
  "tree": "0a85a055fd2cb0cd70329571989e9a2573747bda",
  "parents": [
    "fbf8bc10a466c498fc80c6b58c939a87a8d9e929"
  ],
  "author": {
    "name": "Richard Levasseur",
    "email": "rlevasseur@google.com",
    "time": "Fri Jan 03 10:42:37 2025 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Jan 03 18:42:37 2025 +0000"
  },
  "message": "chore: add check for version_next markers (#2542)\n\nIn a couple recent PRs, I put \"VERSION_NEXT_{feature,patch}\" as place\nholders since I\nwasn\u0027t sure what the next appropriate version would be for unreleased\ncode. e.g.\nspecifying `1.0.1` becomes invalid if a subsequent PR would make it\n`1.1.0`.\n\nTo help remind us to populate these values before a release, have the\nrelease workflow\ncheck for the marker strings.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0bc14f936badaf5bc758ed0f136ddac79d9d8836",
      "old_mode": 33261,
      "old_path": ".github/workflows/create_archive_and_notes.sh",
      "new_id": "b425de96ac76683cc38350885965fec72c49e46a",
      "new_mode": 33261,
      "new_path": ".github/workflows/create_archive_and_notes.sh"
    },
    {
      "type": "modify",
      "old_id": "d5f24a9365526609b18805909353b27504bce734",
      "old_mode": 33188,
      "old_path": "CONTRIBUTING.md",
      "new_id": "8928246c93f04a111a2842e73d3f95388a48bc66",
      "new_mode": 33188,
      "new_path": "CONTRIBUTING.md"
    }
  ]
}