)]}'
{
  "commit": "b16ed8d0c2bd7560e3b4c50a5a54c634d3c34bee",
  "tree": "4fd9c28f6c144bc8d3498a627ade524d8ec7799f",
  "parents": [
    "b54d59343a87e7f27f4cd9b9f9e662e529352259"
  ],
  "author": {
    "name": "TypeScript Team",
    "email": "noreply@google.com",
    "time": "Mon Nov 25 12:41:38 2019 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Nov 25 12:41:59 2019 -0800"
  },
  "message": "Fix generic comparisons on protobuf messages\n\nGenerated protobuf messages contain internal data structures\nthat general purpose comparison functions (e.g., reflect.DeepEqual,\npretty.Compare, etc) do not properly compare. It is already the case\ntoday that these functions may report a difference when two messages\nare actually semantically equivalent.\n\nFix all usages by either calling proto.Equal directly if\nthe top-level types are themselves proto.Message, or by calling\ncmp.Equal with the cmp.Comparer(proto.Equal) option specified.\nThis option teaches cmp to use proto.Equal anytime it encounters\nproto.Message types.\n\nPiperOrigin-RevId: 282412693\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "90a1c1a9c0601ff069cfc633157a67209da1ae4d",
      "old_mode": 33188,
      "old_path": "internal/ts_repositories.bzl",
      "new_id": "30cb4053f65724cc09b2539df4c19c6f689415cd",
      "new_mode": 33188,
      "new_path": "internal/ts_repositories.bzl"
    },
    {
      "type": "modify",
      "old_id": "ff529b8d79628b5982215e2b146edeb5aedff5b3",
      "old_mode": 33188,
      "old_path": "ts_auto_deps/analyze/analyze_test.go",
      "new_id": "7a7d90af3c2ddde64ef8728c1123c4e64d5255b8",
      "new_mode": 33188,
      "new_path": "ts_auto_deps/analyze/analyze_test.go"
    }
  ]
}