)]}'
{
  "commit": "935c5925908fb06de2e70aabdb75630fc876e41e",
  "tree": "73cd86853d60b902e64ef992dafb024726632003",
  "parents": [
    "19cca472c50df7e115dcdb30318ca5454d1df26f"
  ],
  "author": {
    "name": "Alexei Frolov",
    "email": "frolv@pigweed.infra.roller.google.com",
    "time": "Wed Aug 12 20:28:19 2026 -0700"
  },
  "committer": {
    "name": "CQ Bot Account",
    "email": "pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed Aug 12 20:28:19 2026 -0700"
  },
  "message": "roll: third_party/pigweed pw_async2: Make FutureOrValue movable\n\nFutureOrValue originally was not movable as a strict way to enforce that\nusers cannot misuse it by returning it from fuctions. However, this\nprecludes a common, valid use case where FutureOrValue is stored within\na composite future, which must be movable by definition.\n\nThis removes the move restriction on FutureOrValue, instead adding\nstronger wording to the doc about how and how not to use it.\n\nOriginal-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/453972\nOriginal-Revision: 33efd737cc1ffcb78a3e6592e72e84ea2fd90abc\n\nRolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed\nRolled-Commits: 823869564abc12..33efd737cc1ffc\nRoll-Count: 1\nRoller-URL: https://cr-buildbucket.appspot.com/build/8673617319990486849\nGitWatcher: ignore\nCQ-Do-Not-Cancel-Tryjobs: true\nChange-Id: I333d8ce7e7667daea674a6d707b1fe6637499275\nReviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/454405\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "823869564abc125d82409282ac8f3c301d0534d6",
      "old_mode": 57344,
      "old_path": "third_party/pigweed",
      "new_id": "33efd737cc1ffcb78a3e6592e72e84ea2fd90abc",
      "new_mode": 57344,
      "new_path": "third_party/pigweed"
    }
  ]
}