)]}'
{
  "commit": "f41e3b75b4130a12178b7f69211617b4f52caa17",
  "tree": "f168a0845e917e24c2e21382ab6b60e2bd8a6c62",
  "parents": [
    "97e92b82e9e5640c1ffb98bf959bfb187cac989e"
  ],
  "author": {
    "name": "Oliver Newman",
    "email": "olivernewman@fuchsia.infra.roller.google.com",
    "time": "Wed Apr 23 08:41:22 2025 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Apr 23 08:42:39 2025 -0700"
  },
  "message": "[roll] Roll infra/recipes [release] Handle fuchsia.git as an \u003cimport\u003e\n\nhttp://tqr/979232 switched fuchsia.git\u0027s Jiri manifest entry in\nintegration.git from a \u003cproject\u003e to an \u003cimport\u003e. Now the \u003cproject\u003e entry\nfor fuchsia.git is actually in fuchsia.git, but the pinned revision is\nstill attached to the \u003cimport\u003e in integration.git.\n\nThe release operation recipes previously assumed that every repository\u0027s\npinned revision was attached to a \u003cproject\u003e. Now that that is no longer\nthe case, the release operations need to be able to handle fuchsia.git\nin its new state.\n\nThis is very much a quick-and-dirty hack, long-term we should figure out\na way to make this more generic and avoid hardcoding fuchsia.git\u0027s\nproject name and manifest path.\n\nThere\u0027s also going to be more work required to make these recipes work\nwith projects that are pinned in fuchsia.git.\n\nOriginal-Bug: 385378627\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1258664\nOriginal-Revision: efb8df58b7efc21182cbfe94991f4bae36c3e2ee\nGitOrigin-RevId: 8bf502f56f19e791586e96d1b549d878498e8c09\nChange-Id: Icfe3b21271f99bce0caaddeb7c05e21ab1417114\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5c13c4ebaa830a0200781d7fcdc80ba43609ccf5",
      "old_mode": 33188,
      "old_path": "infra/recipes",
      "new_id": "a3fa7667507f665c841fafb7dfdfb3062aa1c16b",
      "new_mode": 33188,
      "new_path": "infra/recipes"
    }
  ]
}