)]}'
{
  "commit": "285a3da07d34c7792d1f4ad44dd5b4d0899e57db",
  "tree": "4b0d210e3b559e9126f87d63be1fdb59c5c13b2c",
  "parents": [
    "d34b30f3ac55843543aa0e534a7e6db12c88a0bb"
  ],
  "author": {
    "name": "gBMC Team",
    "email": "gbmc-core@google.com",
    "time": "Fri Sep 25 14:14:58 2026 -0700"
  },
  "committer": {
    "name": "mdb:gbmc-git-owners",
    "email": "superproject-auto-update@invalid",
    "time": "Fri Sep 25 14:16:43 2026 -0700"
  },
  "message": "component_integrity: Handle Configuration.MCTPUSBDevice\n\nWhen resolving protected component links for ComponentIntegrity and\nTrustedComponent resources, bmcweb failed to match D-Bus objects\nimplementing xyz.openbmc_project.Configuration.MCTPUSBDevice. This caused\nbmcweb to treat them as unsupported resource types and return\nBase.1.13.0.InternalError (HTTP 500).\n\nOn platforms like Velorum, ConnectX-9 SMAs (and other onboard MCUs) are\nmodeled in Entity-Manager as exposed MCTPUSBDevice entities under their\nparent board (e.g. NvidiaMcuSwitch), advertising Configuration.MCTPUSBDevice\nrather than Inventory.Item.Component.\n\nThis change adds Configuration.MCTPUSBDevice to componentItemInterfaces so\nthat bmcweb resolves their parent chassis URI dynamically through either\ntheir contained_by association or the parent path fallback (e.g.\n/redfish/v1/Chassis/NvidiaMcuSwitch).\n\nUnit tests are added for both ComponentIntegrity and TrustedComponent\nhandlers covering both the contained_by association path and the parent-path\nfallback path.\n\nTested: https://paste.googleplex.com/5359464295825408\nTested attestation: https://paste.googleplex.com/4800424876572672\nPiperOrigin-RevId: 988488575\nChange-Id: Id44148c822c95f2eb7e617c7ee7c7cfdf2f502be\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b9ddffb47e8b7ca95d48735b831bcc32d70b5bf",
      "old_mode": 57344,
      "old_path": "gbmcweb",
      "new_id": "a4783aa61688ad96142e95bb72948ed5307b9678",
      "new_mode": 57344,
      "new_path": "gbmcweb"
    }
  ]
}