-
Notifications
You must be signed in to change notification settings - Fork 200
Release process: use github actions and release to bazel central registry #345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note, I discussed this a bit with @gregmagolan since this is exactly the same shape as the copy_to_directory Go toolchain we build and publish with https://github.com/aspect-build/bazel-lib - we could probably share the approach. |
@loosebazooka Any chance you can take a look at this, specifically for the BCR release ? |
I think maybe @alexeagle or @thesayyn might have to advise. My bazel expertise is lacking. We could remove the goreleaser stuff and just do the build with bazel and I think we might be good? |
Yes, we need to Bazelify the build process first, and do what Alex is suggesting here.
|
I've seen releases since last update in this issue, is the above plan still accurate? There's also: |
Discussed with @loosebazooka as part of adding a Bazel rule in this repo: we'd like the release process to:
The text was updated successfully, but these errors were encountered: