)]}'
{
  "commit": "e7083019d663b7ef03eea370995dd6c56f128c55",
  "tree": "6552e65df41e2fb92bd1bf76e6fba78c052fae2d",
  "parents": [
    "cd7e10846f97b5cb9b184c87b4ceaf2f1b4b5d3f",
    "5695833d592242b6c07a9f891c31b1461f23e019"
  ],
  "author": {
    "name": "tonyaiuto",
    "email": "tony.aiuto@gmail.com",
    "time": "Thu Apr 10 22:48:39 2025 -0400"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Apr 10 22:48:39 2025 -0400"
  },
  "message": "feat: support raw symlinks from declare_symlink() (#930)\n\nUsing the `ctx.actions.declare_symlink()` API, rules can create explicit\nsymlinks to arbitrary\npaths, which Bazel will keep as symlinks. The packaging logic treats\nthese\nas regular files, so tries to read through them and store the content\nthey point to. This\nis incorrect for two reasons: they are supposed to be left as symlinks\nand may be dangling\nsymlinks from the perspective of packaging.\n\nTo fix, introduce a new type of file entry: `raw_symlink`. These entries\nmean the `src` is\na symlink whose stored path should be stored into the destination\nverbatim, also as a symlink.\nSuch artifacts are identified using `File.is_symlink`, a Bazel 8+ API.\n\nWork towards https://github.com/bazelbuild/rules_pkg/issues/929",
  "tree_diff": []
}