)]}'
{
  "commit": "af341ad5e59a6b68d5ff7b0c860e3d8f7e201a9b",
  "tree": "2ab25aff83c9e33d9c29b797fc1b9a199f2c18cf",
  "parents": [
    "bf481657f8f2118587dddc63b9f389f2243a5358"
  ],
  "author": {
    "name": "Nicholas S. Husin",
    "email": "nsh@golang.org",
    "time": "Wed Aug 26 15:15:02 2026 -0400"
  },
  "committer": {
    "name": "Nicholas Husin",
    "email": "nsh@golang.org",
    "time": "Wed Aug 26 14:17:44 2026 -0700"
  },
  "message": "internal/http3: do not treat 1xx status as the final response status\n\nTestServer1xxExpect100ContinueRace is flaky for HTTP/3 in std. This is\nbecause duplicate status 100 can cause the HTTP/3 transport to\naccidentally treat 100 as the final response status.\n\nMake sure that 1xx headers are always treated as informational status\nrather than the final status.\n\nFor golang/go#70914\nFor golang/go#81119\n\nChange-Id: Id834c403ae565ed00aa03ac89f69b7286a6a6964\nReviewed-on: https://go-review.googlesource.com/c/net/+/822544\nReviewed-by: Damien Neil \u003cdneil@google.com\u003e\nLUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cgolang-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\nReviewed-by: Nicholas Husin \u003chusin@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "46afe6749bd11831953d80c946e79140c2a29867",
      "old_mode": 33188,
      "old_path": "internal/http3/roundtrip.go",
      "new_id": "a37dad6ed1fb9523cc22c5239e1406f7deaca820",
      "new_mode": 33188,
      "new_path": "internal/http3/roundtrip.go"
    },
    {
      "type": "modify",
      "old_id": "814233b456f76a258c9e1f70707de0a23f69431f",
      "old_mode": 33188,
      "old_path": "internal/http3/roundtrip_test.go",
      "new_id": "8c27fafe2c8cdc0d8c804441b5ced82b436ca085",
      "new_mode": 33188,
      "new_path": "internal/http3/roundtrip_test.go"
    }
  ]
}
