)]}'
{
  "commit": "121898f17d44bc41e56796fbc1da019a266b209e",
  "tree": "ffd8ebc08d604cef12bf875a4000c4d11f95a6a8",
  "parents": [
    "1203af123a47223ff6e560a8d3aabb491e732f28"
  ],
  "author": {
    "name": "Guillaume Nodet",
    "email": "gnodet@gmail.com",
    "time": "Sat Oct 17 07:55:20 2026 +0200"
  },
  "committer": {
    "name": "Guillaume Nodet",
    "email": "gnodet@gmail.com",
    "time": "Sat Oct 17 07:55:20 2026 +0200"
  },
  "message": "docs: add Maven 4 plugin visibility section\n\nDocument how Maven 4 plugins (using maven-di) have a stricter\ncomponent visibility model than Maven 3 plugins (using Sisu):\nMaven 4 mojos are instantiated by a plain maven-di injector with\nonly their own classpath and manually bound core services, without\naccess to build extension components or Sisu beans.\n\nCo-Authored-By: Claude Opus 4.6 (1M context) \u003cnoreply@anthropic.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bebf98fd8a9b2ebc0539962c73ebe12e308453d5",
      "old_mode": 33188,
      "old_path": "src/site/markdown/classloading.md",
      "new_id": "add166453831216422bf8cdcc11a0313b6564246",
      "new_mode": 33188,
      "new_path": "src/site/markdown/classloading.md"
    }
  ]
}