)]}'
{
  "commit": "03ddaacda7ca04656dd32bfbad56121cf4108dc7",
  "tree": "c6c12ffc55e7261ffd1950b1d715e032869c6eeb",
  "parents": [
    "a018953688f1b10bddf91bff8747068f5f4746a4"
  ],
  "author": {
    "name": "Harald Nordgren",
    "email": "haraldnordgren@gmail.com",
    "time": "Tue Oct 27 08:32:15 2026 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Oct 27 07:31:05 2026 -0700"
  },
  "message": "ci: drop quarantine removal for macos perforce binaries\n\nThe xattr -d call that strips com.apple.quarantine from the macOS\nperforce binaries has been doing nothing for years, and can simply\ngo.\n\n5ed9fc3fc8 (ci: prevent `perforce` from being quarantined,\n2020-02-27) added that call to stop p4d -V from hanging on a GUI\nconfirmation dialog that never comes on a CI box, back when perforce\nwas installed via Homebrew\u0027s --no-quarantine cask flag. When\n49af448197 (ci: reintroduce prevention from perforce being\nquarantined in macOS, 2022-05-12) replaced that with a plain wget\nand tar download, it kept the xattr -d call as a precaution, while\nnoting that it already does nothing on GitHub Actions.\n\nA file downloaded with wget never gets com.apple.quarantine set in\nthe first place, only Safari, Finder, and AirDrop apply that\nattribute through the LaunchServices quarantine API. The same holds\non GitLab CI\u0027s macOS runners, so the call has been a silent no-op\neverywhere since 2022.\n\nSigned-off-by: Harald Nordgren \u003charaldnordgren@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d57dce566301738cb06c897ecdbdccc69446163e",
      "old_mode": 33261,
      "old_path": "ci/install-dependencies.sh",
      "new_id": "203e8401cfd364ff305267d0363d8e53ce6a839b",
      "new_mode": 33261,
      "new_path": "ci/install-dependencies.sh"
    }
  ]
}
