)]}'
{
  "commit": "1f6609d02ea604de859d8c417ea1828846a6ccf5",
  "tree": "f38e6d171810b3525039b6b06f8c2ff1e6c73530",
  "parents": [
    "5bfb61b2ab059ee2e1a3931e1c5c32ee7e8471f1"
  ],
  "author": {
    "name": "Oliver Newman",
    "email": "olivernewman@fuchsia.infra.roller.google.com",
    "time": "Tue Dec 10 06:55:53 2024 +0000"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Dec 09 22:57:43 2024 -0800"
  },
  "message": "[roll] Roll infra/recipes [submodule_roller] Force-clone the submodule to roll\n\n... even if they have `update \u003d none` in the .gitmodules file. It\u0027s not\npossible to update the submodule without cloning it.\n\nA previous attempt at rolling submodules with `update \u003d none`\n(https://fxrev.dev/1170332) attempted to do it by skipping cloning the\nsubmodule and directly updating the git index. However, this didn\u0027t\ninteract nicely with the auto_roller recipe module\u0027s no-op change\ndetection logic, which didn\u0027t consider the submodule to be changed.\n\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1170958\nOriginal-Revision: ec1be15e19abe850ddb469c7bf35f5f79a076027\nGitOrigin-RevId: 8dc58ed217cca66fada2cced77a7acc84a4cd74f\nChange-Id: I43145ad9cc2983e4b46e58b63da15fd67a5810e3\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2516102267e721dcc71c637c79ea57e5a8bfd44b",
      "old_mode": 33188,
      "old_path": "infra/recipes",
      "new_id": "a1c4f7a05491643b6fc726e3d808832ff855f0b0",
      "new_mode": 33188,
      "new_path": "infra/recipes"
    }
  ]
}