)]}'
{
  "commit": "420780fc2d59ee986cdf2244b041520a6f79f643",
  "tree": "6a3004761ce78d4786df4303e9f5fdec5644c116",
  "parents": [
    "9058febd4ab32dbf873a2044ab0be87a664be290"
  ],
  "author": {
    "name": "David Ostrovsky",
    "email": "david.ostrovsky@gmail.com",
    "time": "Thu Jul 02 01:51:49 2026 -0700"
  },
  "committer": {
    "name": "David Ostrovsky",
    "email": "david.ostrovsky@gmail.com",
    "time": "Thu Jul 02 01:56:35 2026 -0700"
  },
  "message": "Exempt MODULE.bazel from Library-Compliance requirement\n\nGerrit’s external Maven dependencies relevant for Library-Compliance are\nnow declared through the rules_jvm_external TOML input tools/deps.toml\nand wired from tools/java_deps.MODULE.bazel.\n\ntools/deps.toml already requires Library-Compliance approval. It is the\nauthoritative place for third-party library coordinates and versions\nthat are relevant for Google.\n\nThe root MODULE.bazel mostly declares Bazel modules and build rules,\nsuch as rules_java, rules_nodejs, rules_jvm_external, and local module\nwiring. These Bazel module dependencies are not the library dependencies\nconsumed by Google, and requiring Library-Compliance approval for every\nMODULE.bazel change creates unnecessary review friction.\n\nKeep Library-Compliance focused on the files that actually define\nrelevant external library metadata.\n\nAs part of this cleanup, also remove the obsolete maven_install.json\nentry from the submit requirement. It was left over from the bzlmod\nmigration, and the file no longer exists.\n\nChange-Id: I698df8ef0df5566af6d426db01f9bd15da89fda1\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "41f5e5cea1f80a38faae51873efdb9d183c69033",
      "old_mode": 33188,
      "old_path": "project.config",
      "new_id": "7d6b6c06c95b3fb8ba93b5f2547ad49fac6d465e",
      "new_mode": 33188,
      "new_path": "project.config"
    }
  ]
}