Repository navigation
release: include macOS binaries in GoReleaser artifacts - #157
SriVishnu230707 wants to merge 1 commit into
Conversation
|
But this doesn't address the notarization concerns, so what does this add? |
|
You're right. This adds unsigned macOS archives and cross-build coverage, but it doesn't address signing or notarization. Those archives wouldn't provide the smooth install path that #149 asks for, so my I don't want to add release artifacts that conflict with the project's Homebrew direction. Would a signed and notarized release path be something you'd want pursued here once the project has the required Apple credentials, or would you prefer I close this PR? I can move any independently useful release checks into a separate PR. |
|
I'll close this for now. If I ever work up the energy to fight the Apple release mechanisms then I'll reconsider this. But for now, Mac users should either use homebrew, nix, or compile from source themselves. |
This proposal adds macOS tar.gz artifacts for amd64 and arm64, plus release-tagged cross-build checks and installation/release documentation. The unsupported darwin/arm target is excluded.
Review status: These archives are unsigned and unnotarized. As Brad pointed out in the discussion, this does not yet solve the macOS installation concern in #149. I am awaiting maintainer direction on whether a signed and notarized release path is wanted before changing the release workflow further.
Validation: cross-built
cmd/tailcatfor darwin/amd64 and darwin/arm64 withCGO_ENABLED=0and release build tags; both passed.git diff --checkpassed.