)]}'
{
  "commit": "9e6e5bf94d14b2f480473decd52eb9a5e8baa09b",
  "tree": "eba06f22162a913e49ed46e2df13d305c9dc5e99",
  "parents": [
    "dabbc2815588ec43bb980dbb8e7f1c89896344de"
  ],
  "author": {
    "name": "A Googler",
    "email": "no-reply@google.com",
    "time": "Wed Aug 19 10:26:48 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Aug 19 10:27:32 2026 -0700"
  },
  "message": "Default output_jar_creator to bazel in apk_packaging.bzl.\n\nIn CL 959227250, output_jar_creator was defaulted to \"bazel\" in\nrules/java.bzl:singlejar, and removed from rules/android_binary/impl.bzl.\nHowever, rules/apk_packaging.bzl still defaulted output_jar_creator \u003d \"\"\nin _process() and output_jar_creator \u003d None in _build_apk(), and forwarded\nthe argument to java.singlejar().\n\nBecause rules/java.bzl checks `if output_jar_creator:`, passing \"\" or None\ncaused the \"bazel\" default to be bypassed for base module packaging,\nproducing \"Created-By: singlejar\" (48 bytes). Feature modules, which call\njava.singlejar() directly, picked up \"Created-By: bazel\" (44 bytes),\ntriggering Bundletool EntryClashValidator InvalidBundleException.\n\nDefaulting output_jar_creator \u003d \"bazel\" in both _process() and _build_apk()\nensures consistent 44-byte MANIFEST.MF headers across all module splits.\n\nPiperOrigin-RevId: 967283865\nChange-Id: I3bfe26031f086a23cd2912bc07e2452604668952\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e7722074f998625253c131d3a5d489e07fffd47c",
      "old_mode": 33188,
      "old_path": "rules/apk_packaging.bzl",
      "new_id": "7fe189639c8fb850a3b3b5e2f53b59b498ca8494",
      "new_mode": 33188,
      "new_path": "rules/apk_packaging.bzl"
    }
  ]
}