)]}'
{
  "commit": "abd8d37c999fa3c9ca71c2f0cfb98e6bf2201894",
  "tree": "fb16777c6a9a977f6b7943cb7fb664d88861b425",
  "parents": [
    "601ed1be013a1deb31b44a15d0452eab71eee4e8"
  ],
  "author": {
    "name": "stuartmorgan-g",
    "email": "stuartmorgan@google.com",
    "time": "Sun Jun 14 14:45:30 2026 -0400"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Jun 14 18:45:30 2026 +0000"
  },
  "message": "Rework docs for flutter/packages changelogs (#187666)\n\nUpdating CHANGELOGs correctly is one of the most common issues for new\ncontributors in flutter/packages. The way the docs were written\nhighlights using the `NEXT` section for version-exempt changes first,\nbecause it\u0027s unusual and specific to our repo, but given how common it\nis for new contributors to use it when they shouldn\u0027t, it seems like\nthis structure is likely confusing for the people who most need the\ndocs.\n\nThis reworks the whole section to discuss the common case first, then\nthe uncommon case (now explicitly highlighted as uncommon) second. The\nnew structure is a little longer, but should hopefully be more clear,\nwhich seems like a tradeoff worth trying given the frequency of issues.\n\nAlso includes some minor fixes I noticed while I was in the file\n(grammar, inconsistent backticks for file names), and addition of\nreferences to the new flutter/core-packages.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cda7ad1c6f1ad1c28369dd9db9e670db8115a5a1",
      "old_mode": 33188,
      "old_path": "docs/ecosystem/contributing/README.md",
      "new_id": "3fdd223ebd26c4518951346fead730a76c65d5af",
      "new_mode": 33188,
      "new_path": "docs/ecosystem/contributing/README.md"
    }
  ]
}