)]}'
{
  "commit": "53996535fb17cf5fd9b4d3f6b3ae96af74add1e8",
  "tree": "394a290540cfe630c25b0f290072c902eb3d868c",
  "parents": [
    "361240455fd9c7fd53b270d0b508b418de4bb763",
    "b3b1ad91b2a5559a6aeaaef28faf8979a37e5259"
  ],
  "author": {
    "name": "tonyaiuto",
    "email": "tony.aiuto@gmail.com",
    "time": "Mon Mar 02 21:54:19 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Mar 02 21:54:19 2026 -0500"
  },
  "message": "Create release scripts for rules_pkg_providers (#1028)\n\n- create a new release_module workflow\n  - takes subdir and version as args, default to `providers` for now. \n  - stole the buildifier technique we used in supply_chain\n  - the code should work for toolchains if we split that.\n- modify release_prep.sh to deal with old and new styles\n- we need an ugly case statement because the release workflow we use\ndoes not take the release_prep script name as a parameter.\n   - ideally, I would do things from #1031, but that\u0027s less urgent.\n\nHand testing release_prep.sh seems to work. Testing the workflow is\nnearly impossible until it exists the first time.\n\nNext steps:\n- verify it works\n- figure out something for BCR releases.\n- Hope for: https://github.com/bazel-contrib/publish-to-bcr/issues/368\n- more pragmatic solution might be to have a shell script around the bcr\nadd-module script\n\nFuture work:\n- generate git changelog on a per-subdir basis.\n- allow better customization of release notes documentation link.",
  "tree_diff": []
}