)]}'
{
  "commit": "7f1d59e750ba510dcbc985e8cd94413b5434981e",
  "tree": "abe5c26a016d19d4eea332a7caf612c8616ada3e",
  "parents": [
    "82054683dd7ecd6db2304e8a26e6b1b6f2497da9"
  ],
  "author": {
    "name": "Jeremy Volkman",
    "email": "jeremy@cedarai.com",
    "time": "Sat Jun 15 21:14:40 2024 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Jun 16 04:14:40 2024 +0000"
  },
  "message": "fix(bzlmod): use same target in requirement(\u0027foo\u0027) and all_requirements (#1973)\n\nWe have at least one instance in our pre-bzlmod workspace like:\n```\ndeps \u003d list(all_requirements)\ndeps.remove(requirement(\u0027foo\u0027))\n```\n\nBut when using bzlmod, the generated `all_requirements` list contains\ntargets like `@@rules_python~~pip~my_deps//sqlalchemy:sqlalchemy`,\nwhereas `requirement(\u0027sqlalchemy\u0027)` will return\n`@@rules_python~~pip~my_deps//sqlalchemy:pkg`. So this operation now\nfails.\n\nThis change makes `all_requirements` also use the `:pkg` targets to\nmatch `requirement`.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ba7045a70b2bf713f4a889d31bd8117245b2ac5",
      "old_mode": 33188,
      "old_path": "CHANGELOG.md",
      "new_id": "e39239418aa21ced67513cef432f1d2a20b1651c",
      "new_mode": 33188,
      "new_path": "CHANGELOG.md"
    },
    {
      "type": "modify",
      "old_id": "0f962031d66cb3576745d561a3b69dec9fb3290a",
      "old_mode": 33188,
      "old_path": "python/private/bzlmod/pip_repository.bzl",
      "new_id": "d42eb8b0566de3fdf15002dcbb67075a929c1157",
      "new_mode": 33188,
      "new_path": "python/private/bzlmod/pip_repository.bzl"
    }
  ]
}