I implemented some Bazel rules (bzlrelease) that work with a GitHub Actions workflow to create releases for my Bazel rule repositories. In short, it generates the release notes along with a workspace snippet, creates the GitHub release, and creates an auto-merge PR to update the README.md with the latest workspace snippet.
All of the pre-requisites are already being loaded in this repository. I would add a release Bazel package that would contain a BUILD file, README.md file, and a workspace snippet template (i.e., contains the load statements that need to be added to client workspaces). I would update the repository's README.md to include two markers as markdown comments to indicate where to insert/replace the generated workspace snippet. Releases can be created using a Bazel run command or via the GitHub Actions web interface.
keith
commented
2 years ago
I implemented some Bazel rules (bzlrelease) that work with a GitHub Actions workflow to create releases for my Bazel rule repositories. In short, it generates the release notes along with a workspace snippet, creates the GitHub release, and creates an auto-merge PR to update the
README.mdwith the latest workspace snippet.All of the pre-requisites are already being loaded in this repository. I would add a
releaseBazel package that would contain aBUILDfile,README.mdfile, and a workspace snippet template (i.e., contains the load statements that need to be added to client workspaces). I would update the repository'sREADME.mdto include two markers as markdown comments to indicate where to insert/replace the generated workspace snippet. Releases can be created using a Bazel run command or via the GitHub Actions web interface.If you would like to see an actual implementation, here is the release package, the GitHub Actions workflow and a release generated by this process for
cgrindel/bazel-starlib. I could add this pretty quickly if you are interested.