)]}'
{
  "commit": "6adb624e04b0c6a0f4c5c06d3685f4ca2be7691d",
  "tree": "9451a525f123ee578c58771196c460e06ac841fa",
  "parents": [
    "ff8a62a3fb9214aaaa111a2c0a488985002873fc"
  ],
  "author": {
    "name": "Alon Zakai",
    "email": "azakai@google.com",
    "time": "Tue Aug 11 15:10:43 2020 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Aug 11 15:10:43 2020 -0700"
  },
  "message": "Error on trying to get latest-fastcomp (#590)\n\nI think this is less surprising than continuing to support latest-fastcomp\r\nwith the last fastcomp release. That\u0027s technically correct - the last release\r\nis 1.40.1, and always will be - but when a user asks for \"latest\" I think they\r\nwant something up to date. Instead, give a clear error that indicates how\r\nthey can get an actually up to date build, by using upstream.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0b7a4a2ce9da9b6a96595d2b3edab980744175f7",
      "old_mode": 33261,
      "old_path": "emsdk.py",
      "new_id": "89e9d68f7d0f355bbd689a42a50605db27edbc1e",
      "new_mode": 33261,
      "new_path": "emsdk.py"
    },
    {
      "type": "modify",
      "old_id": "03a1acebfc8b4f8aad59b633c1f3e7d89bfbe044",
      "old_mode": 33261,
      "old_path": "scripts/test.py",
      "new_id": "beee4ace8df71a50a0b17d622e9fa5629d793d61",
      "new_mode": 33261,
      "new_path": "scripts/test.py"
    }
  ]
}