Repository navigation
distribution: GoReleaser config for Homebrew + Scoop + ghcr.io - #121
Merged
Merged
Conversation
13 of 15 tasks
noeljackson
added a commit
that referenced
this pull request
May 15, 2026
…#88) (#121) Per user direction: do it via goreleaser config, not by setting up brewed scripts or push pipelines manually. ## What the config publishes per `v*` tag push - **Pre-built binaries** (existing): linux / darwin / windows × amd64 / arm64 tarballs + zip, sha256 checksums. - **Homebrew formula** in `noeljackson/homebrew-deepsec` — goreleaser generates and pushes via `HOMEBREW_TAP_TOKEN`. Install becomes `brew install noeljackson/deepsec/deepsec`. - **Scoop manifest** in `noeljackson/scoop-deepsec` — `scoop bucket add deepsec ...; scoop install deepsec`. - **Docker images** at `ghcr.io/noeljackson/deepsec:{Version,latest}` — multi-arch (amd64 + arm64) via buildx + a separate `Dockerfile.goreleaser` (the existing Dockerfile builds from source; the goreleaser one just COPYs the prebuilt binary onto distroless). - **Native packages** — .deb, .rpm, .apk uploaded as release assets via nfpms (no third-party repo needed; users `dpkg -i` / `rpm -ivh` the asset directly). ## Workflow changes (`release.yml`) - Adds QEMU + buildx setup for multi-arch container builds - Adds ghcr.io login step using `GITHUB_TOKEN` - Passes `HOMEBREW_TAP_TOKEN` + `SCOOP_TAP_TOKEN` env to goreleaser ## Setup the user needs to do once 1. Create empty repos: `github.com/noeljackson/homebrew-deepsec` and `github.com/noeljackson/scoop-deepsec`. 2. Create a fine-grained GitHub token with **Contents: Read+Write** on both tap repos. Add it as `HOMEBREW_TAP_TOKEN` and `SCOOP_TAP_TOKEN` secrets on `noeljackson/deepsec`. 3. Tag a release (`git tag v0.2.0 && git push origin v0.2.0`); the workflow does the rest. After the first run, README install one-liners are accurate. ## Goreleaser-check passes `goreleaser check`: 1 configuration file(s) validated. Two deprecation notes — `dockers`/`brews` v1 will be replaced by `dockers_v2`/`homebrew_casks` in a future goreleaser. v1 keys still work in current goreleaser v2; we'll migrate when v3 lands. ## README install section rewritten Now leads with brew / scoop / docker / native packages; `go install` demoted to "for main builds." `docker build` instructions still present but moved below the published-image one-liner. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
noeljackson
added a commit
that referenced
this pull request
May 18, 2026
…#88) (#121) Per user direction: do it via goreleaser config, not by setting up brewed scripts or push pipelines manually. ## What the config publishes per `v*` tag push - **Pre-built binaries** (existing): linux / darwin / windows × amd64 / arm64 tarballs + zip, sha256 checksums. - **Homebrew formula** in `noeljackson/homebrew-deepsec` — goreleaser generates and pushes via `HOMEBREW_TAP_TOKEN`. Install becomes `brew install noeljackson/deepsec/deepsec`. - **Scoop manifest** in `noeljackson/scoop-deepsec` — `scoop bucket add deepsec ...; scoop install deepsec`. - **Docker images** at `ghcr.io/noeljackson/deepsec:{Version,latest}` — multi-arch (amd64 + arm64) via buildx + a separate `Dockerfile.goreleaser` (the existing Dockerfile builds from source; the goreleaser one just COPYs the prebuilt binary onto distroless). - **Native packages** — .deb, .rpm, .apk uploaded as release assets via nfpms (no third-party repo needed; users `dpkg -i` / `rpm -ivh` the asset directly). ## Workflow changes (`release.yml`) - Adds QEMU + buildx setup for multi-arch container builds - Adds ghcr.io login step using `GITHUB_TOKEN` - Passes `HOMEBREW_TAP_TOKEN` + `SCOOP_TAP_TOKEN` env to goreleaser ## Setup the user needs to do once 1. Create empty repos: `github.com/noeljackson/homebrew-deepsec` and `github.com/noeljackson/scoop-deepsec`. 2. Create a fine-grained GitHub token with **Contents: Read+Write** on both tap repos. Add it as `HOMEBREW_TAP_TOKEN` and `SCOOP_TAP_TOKEN` secrets on `noeljackson/deepsec`. 3. Tag a release (`git tag v0.2.0 && git push origin v0.2.0`); the workflow does the rest. After the first run, README install one-liners are accurate. ## Goreleaser-check passes `goreleaser check`: 1 configuration file(s) validated. Two deprecation notes — `dockers`/`brews` v1 will be replaced by `dockers_v2`/`homebrew_casks` in a future goreleaser. v1 keys still work in current goreleaser v2; we'll migrate when v3 lands. ## README install section rewritten Now leads with brew / scoop / docker / native packages; `go install` demoted to "for main builds." `docker build` instructions still present but moved below the published-image one-liner.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #88. Per the user's directive: do it via goreleaser, no manual setup.
🤖 Generated with Claude Code