)]}'
{
  "commit": "2e8b219634f887b90995a2bb0903cb61c4ce9199",
  "tree": "47d2d1ebb708fdd43940cb25517184be9cc4bb68",
  "parents": [
    "6aaf82d9106324195f3902aeca295f07e640be61"
  ],
  "author": {
    "name": "Hong Shin",
    "email": "hongshin@google.com",
    "time": "Thu May 07 07:04:51 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu May 07 07:12:10 2026 -0700"
  },
  "message": "upb: update fuzz util build ext to elide faulty extensions early on\n\nIn some cases, we were constructing invalid extensions. These extensions would have a field # that collided with an extant one, causing us to assert_fail inside upb_ExtensionRegistry_Add.\n\nNow that we check for colliding field #\u0027s, this\u0027ll no longer be possible when constructing fuzz candidates.\n\nPiperOrigin-RevId: 911942039\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "685fd0f166d1410cf712fa705ca4f9db450b7ca4",
      "old_mode": 33188,
      "old_path": "upb/test/fuzz_util.cc",
      "new_id": "7aa78b7f7ce2faaf3851e5a18e511d4ad213cc42",
      "new_mode": 33188,
      "new_path": "upb/test/fuzz_util.cc"
    }
  ]
}