)]}'
{
  "commit": "8a17bff719ee0e59353fb376215186a5356b4db1",
  "tree": "b44f2476e9479e1d8f982b0dd1ce6189d53b0ec2",
  "parents": [
    "67c7844b7f7f228229c037cf297296874f50692c"
  ],
  "author": {
    "name": "David Ostrovsky",
    "email": "david@ostrovsky.org",
    "time": "Sun Aug 16 13:46:57 2026 +0200"
  },
  "committer": {
    "name": "David Ostrovsky",
    "email": "david@ostrovsky.org",
    "time": "Mon Aug 17 21:12:00 2026 -0700"
  },
  "message": "Avoid NullArgumentForNonNullParameter false positive via javac flag\n\nrules_java 9.8.0\u0027s newer Error Prone flags idiomatic Guava calls\n(Iterables.getFirst(x, null); ToStringHelper.add(name, nullable) under\nomitNullValues) as NullArgumentForNonNullParameter. This is a false\npositive rooted in OpenJDK JDK-8225377: before JDK 22, javac does not\nattach type-use annotations loaded from classpath class files to their\nsymbols, so Error Prone cannot see Guava\u0027s @ParametricNullness /\nJSpecify @Nullable and treats the parameter as non-null. It reproduces\non the JDK 21 this repo targets (including the bundled 21.0.12) but not\non JDK 22+.\n\nSee this issue for more details:\nhttps://github.com/bazelbuild/bazel/issues/30743\n\nA TODO tracks removing the javacopt once JavaBuilder passes it upstream.\n\nChange-Id: I3fce51b27ada2a440b55ccb94b2d2e40ffff57c0\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9beefdf2302c6ca709e55298fa05f5dcd25c51ec",
      "old_mode": 33188,
      "old_path": "tools/BUILD",
      "new_id": "8e2863899d793730c4dc03591af9c5f7f531211f",
      "new_mode": 33188,
      "new_path": "tools/BUILD"
    }
  ]
}