We converted the releaserc to json for easier debugging, and now we are able to attach binaries to GitHub releases. Also fixed some permission issues, and named some steps.
As there are currently no releases, when this is merged, it will push v1.0.0. We should wait for #6 to be merged before doing this.
How to test
We tested this by adding the branch name to the release config, triggering the action, observing the release, with the correct binaries attached to it. The release has since been deleted for a clean history
How can we measure success?
Teams are able to download bucket-blocker as a binary, and execute it on their machines
What does this change?
We converted the releaserc to json for easier debugging, and now we are able to attach binaries to GitHub releases. Also fixed some permission issues, and named some steps.
As there are currently no releases, when this is merged, it will push v1.0.0. We should wait for #6 to be merged before doing this.
How to test
We tested this by adding the branch name to the release config, triggering the action, observing the release, with the correct binaries attached to it. The release has since been deleted for a clean history
How can we measure success?
Teams are able to download bucket-blocker as a binary, and execute it on their machines