)]}'
{
  "commit": "583980e24fddd61ebf6c82a7ce33caceb4e353ea",
  "tree": "021727a2be025b861d008f8f8299cf3ca525768c",
  "parents": [
    "0c3e04786949d389a4dad551a93e39ca2e49059c"
  ],
  "author": {
    "name": "Lily Chen",
    "email": "chlily@google.com",
    "time": "Fri Nov 06 17:39:16 2026 +0000"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed Nov 11 17:41:29 2026 -0800"
  },
  "message": "pki: Track the issuing certificate in PathVerifier\n\nPathVerifier tracked the issuer\u0027s subject (RFC 5280\u0027s\nworking_issuer_name) separately from the issuer itself. RFC 5280 splits\nthe issuer into separate variables because its trust anchor need not be\na certificate, but here the trust anchor is always a certificate.\n\nSo track the issuing certificate, so that later changes can read other\nproperties of the issuer, such as the MTC CA extension, when verifying\nthe next certificate.\n\nNo behavior change.\n\nBug: 575507260\nChange-Id: I79eaa48ecbe98d41fff6f6af11368a106a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/105389\nReviewed-by: Matt Mueller \u003cmattm@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Lily Chen \u003cchlily@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9a5943bbb3d5a9e876fbda61281aec9ad6b524b2",
      "old_mode": 33188,
      "old_path": "pki/verify_certificate_chain.cc",
      "new_id": "da4929d8dfbd1dd12a6c94eee2aed7c8e68a679a",
      "new_mode": 33188,
      "new_path": "pki/verify_certificate_chain.cc"
    }
  ]
}
