)]}'
{
  "commit": "42433c6048c0a81e7669d3d9e36fece025185487",
  "tree": "de271487e21fe719a6e0df8c6877015a57020b43",
  "parents": [
    "f13cae11623c6725a7aa15f67572577862d24242"
  ],
  "author": {
    "name": "cpovirk",
    "email": "cpovirk@google.com",
    "time": "Tue Jun 04 12:45:02 2019 -0700"
  },
  "committer": {
    "name": "Ron Shapiro",
    "email": "shapiro.rd@gmail.com",
    "time": "Thu Jun 06 11:06:15 2019 -0400"
  },
  "message": "Update to Truth 0.45, and address deprecations.\n\nRenames may include:\n- containsAllOf \u003d\u003e containsAtLeast\n- containsAllIn \u003d\u003e containsAtLeastElementsIn\n- isSameAs \u003d\u003e isSameInstanceAs\n- isOrdered \u003d\u003e isInOrder\n- isStrictlyOrdered \u003d\u003e isInStrictOrder\n\nThe other major change is to change custom subjects to extend raw Subject instead of supplying type parameters. The type parameters are being removed from Subject. This CL will temporarily produce rawtypes warnings, which will go away when I remove the type parameters (as soon as this batch of CLs is submitted).\n\nSome CLs in this batch also migrate calls away from actualAsString(). Its literal replacement is `\"\u003c\" + actual + \"\u003e\"` (unless an object overrides actualCustomStringRepresentation()), but usually I\u0027ve made a larger change, such as switching from an old-style \"Not true that...\" failure message to one generated with the Fact API. In that case, the new code usually contains a direct reference to this.actual (a field that I occasionally had to create). Another larger change I sometimes made is to switch from a manual check-and-fail approach to instead use check(...). And sometimes I just remove a withMessage() call that\u0027s no longer necessary now that the code uses check(...), or I introduce a check(...) call. (An assertion made with check(...) automatically includes the actual value from the original subject, so there\u0027s no need to set it again with withMessage().)\n\nFinally, there\u0027s one CL in this batch in which I migrate a Correspondence subclass to instead use Correspondence.from.\n\n-------------\nCreated by MOE: https://github.com/google/moe\nMOE_MIGRATED_REVID\u003d251495286\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "77e677d5517a57fa2af834410d046e8b9a815523",
      "old_mode": 33188,
      "old_path": "value/pom.xml",
      "new_id": "0fa9223dd4c86220ba8dc1c77080feb2a455e3f6",
      "new_mode": 33188,
      "new_path": "value/pom.xml"
    },
    {
      "type": "modify",
      "old_id": "d4a58971861926e28f2687eaf3c6e5c1f9fccb80",
      "old_mode": 33188,
      "old_path": "value/src/test/java/com/google/auto/value/extension/memoized/MemoizedMethodSubject.java",
      "new_id": "c6888f8f0d6220ffa71e24cb49edff1322b6ecb8",
      "new_mode": 33188,
      "new_path": "value/src/test/java/com/google/auto/value/extension/memoized/MemoizedMethodSubject.java"
    }
  ]
}