You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use GoReleaser for GitHub release workflow (zarf-dev#498)
* use GoReleaser for github release workflow
* add org token for brew recipe pushes
* init command looks for init-package in executable directory
* include init-package in the GoReleaser generated release
* add nerd-note doc about GoReleaser creating a homebrew recipe for Zarf
Copy file name to clipboardexpand all lines: README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -297,7 +297,8 @@ Zarf is written entirely in [go](https://go.dev/), except for a single 400Kb bin
297
297
- An init container runs the rust binary to re-assemble and extract the zarf binary and registry image
298
298
- The container then starts and runs the zarf binary to host the registry image in an embedded docker registry
299
299
- After this, the main docker registry chart is deployed, pulls the image from the ephemeral pod, and finally destroys the created configmaps, pod, and service
300
-
300
+
- We have published a [Homebrew Tap](https://github.com/defenseunicorns/homebrew-tap) for this project that you can install with `brew tap defenseunicorns/tap && brew install zarf`
301
+
- This recipe is updated with each new version release via [GoReleaser](https://goreleaser.com/customization/homebrew/) as part of the release pipeline that runs on GitHub Actions.
0 commit comments