)]}'
{
  "commit": "d7e0f73575322aa9b50c1413e17a6c2838c24208",
  "tree": "936254880152abb5caec5cd2a171c4cebfd69659",
  "parents": [
    "cfb6860620e4d4d0ee3366fd75729dd7d16d24e6"
  ],
  "author": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Wed Jun 24 01:44:34 2026 -0700"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed Jun 24 23:49:52 2026 -0700"
  },
  "message": "SSLBuffer::EnsureCap: ensure `new_cap` can never cause `offset_` overflow.\n\nNote that, as all users of `SSLBuffer` implement their own cap way below\n32k even, there is non way to actually cause this overflow in BoringSSL\nas it is now; making this change merely to ensure no future surprises.\n\nChange-Id: Ia8245a1d25e57c17f750fa2580208c4d6a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/97867\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bb39afaf96fd8760a60536b4b6ae16505690bdae",
      "old_mode": 33188,
      "old_path": "ssl/ssl_buffer.cc",
      "new_id": "e6a2b045cf52ef4d340ec6e3566e37b1ab9793ba",
      "new_mode": 33188,
      "new_path": "ssl/ssl_buffer.cc"
    },
    {
      "type": "modify",
      "old_id": "7f238397f0d7ffe341e5caba62cd960f37e5ebc2",
      "old_mode": 33188,
      "old_path": "ssl/ssl_internal_test.cc",
      "new_id": "bfbf211a5ba747920b6a142832aa93434480cbce",
      "new_mode": 33188,
      "new_path": "ssl/ssl_internal_test.cc"
    }
  ]
}