)]}'
{
  "commit": "e48e1997a21138369b22b74c439aac6f68fd7101",
  "tree": "3771a525d4d47b6ac09044ccd5c46d30dc839c2c",
  "parents": [
    "8267e229a677212e9771a7eb14b259482db20cc9"
  ],
  "author": {
    "name": "Régis Desgroppes",
    "email": "rdesgroppes@gmail.com",
    "time": "Sat Jan 24 17:10:42 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Jan 24 09:10:42 2026 -0700"
  },
  "message": "fix(ci): use own `md5` tool for Bazel 9 compatibility (#1007)\n\nBazel 9.0.0 flipped `--incompatible_strict_action_env` to `true` by\ndefault, restricting `PATH` to `/bin:/usr/bin:/usr/local/bin`.\n\nOn macOS, this broke a few tests relying on the `md5sum` command:\n```\nExecuting genrule //tests/deb:generate_md5sums failed: (Exit 127): [...]\n[...]\n/bin/bash: md5sum: command not found\n```\n\nThis is because:\n1. `md5sum` is not a native macOS command (macOS equivalent is `md5`),\n2. Homebrew\u0027s `md5sum` is typically in `/opt/homebrew/bin`, which is no\n   longer in the restricted `PATH`.\n\nSince the repo already maintains a cross-platform `//tests/util:md5`\ntool, the fix simply consists in leveraging it.\n\nNote on:\n```diff\n-    cmd \u003d \"for i in $(OUTS); do echo 1 \u003e$$i; done\",\n+    cmd \u003d \"for i in $(OUTS); do echo $$i \u003e$$i; done\",\n```\n... is only meant to get distinct md5 sums for the 2 input files used\nin tests.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fa53244c0d0e0e8e671dee43940ecbf637385ec4",
      "old_mode": 33188,
      "old_path": "tests/deb/BUILD",
      "new_id": "b11e66cdeaaa6ccd134fcbe0a6c46eee1f2dd032",
      "new_mode": 33188,
      "new_path": "tests/deb/BUILD"
    }
  ]
}