)]}'
{
  "commit": "d2e363474bb08602c934335d3d80f22c65cc6f8c",
  "tree": "96c9bd75d1b1dfa51ee2cc82568c00e6aa50067c",
  "parents": [
    "768c3a0e928b8c553656419eebb048984794d3e3"
  ],
  "author": {
    "name": "Matan Lurey",
    "email": "matanl@google.com",
    "time": "Mon Jun 16 16:47:25 2025 -0700"
  },
  "committer": {
    "name": "CQ Bot Account",
    "email": "flutter-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Mon Jun 16 16:47:25 2025 -0700"
  },
  "message": "Add optional rel_hash property to release_publish.\n\nThis would allow us to define a specific commit to publish as a tagged\nrelease, instead of the (default) inferred latest commit in a branch; it\nis likely use would be rarer but would still allow a way for us to either\npublish a specific commit, or intentionally publish an older commit.\n\nSee https://github.com/flutter/flutter/issues/170547.\n\nChange-Id: Idab39c8e53c0a98a904c9989fbbcb3038b9916b9\nBug: https://github.com/flutter/flutter/issues/170547\nReviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66662\nReviewed-by: Jason Simmons \u003cjsimmons@google.com\u003e\nCommit-Queue: Matan Lurey \u003cmatanl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "e6b5c76b7003c2a82bcd3f9d03a0992118b92335",
      "new_mode": 33188,
      "new_path": "recipes/release/release_publish.expected/success_manual_rel_hash.json"
    },
    {
      "type": "modify",
      "old_id": "6043dc03a392f3ad2b58a24250e672c299c9cec1",
      "old_mode": 33188,
      "old_path": "recipes/release/release_publish.py",
      "new_id": "8f22e67323c3de9636e912f1ddb02be24b48128e",
      "new_mode": 33188,
      "new_path": "recipes/release/release_publish.py"
    }
  ]
}