Release the .deb and the Homebrew cask with GoReleaser - #4
Merged
Merged
Conversation
Add nfpms and homebrew_casks to the GoReleaser config, and build darwin alongside linux so the cask has something to point at. The deb carries nothing but /usr/bin/specsdeployd: the Ansible role owns the user, the sudoers drop-in, /etc/specsdeployd/ and the unit, and dpkg would silently overwrite them on the next upgrade if the package shipped them too.
Ilyes512
force-pushed
the
feat/GH-2-goreleaser-release
branch
from
September 13, 2026 18:40
b06485b to
392b6c7
Compare
The release workflow floats on '~> v2', so the pin is what makes release:dry-run reproduce what CI will actually run.
13 tasks
13 tasks
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
1 participant
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.
Summary
nfpms(deb, amd64 + arm64) and thespecsdeployd@rc/specsdeploydHomebrew cask pair to.goreleaser.yml; build darwin alongside linux so the cask has an archive to point at./usr/bin/specsdeployd— no unit, no sudoers, no config dir, no maintainer scripts. The Ansible role owns those, and dpkg would silently overwrite them on the next upgrade..github/workflows/release.yml: onv*tags,goreleaser-actionwithcontents: write.Verified against a local snapshot
dpkg -clists the binary and nothing else;dpkg -Ishows no maintainer scripts.dpkg -x+specsdeployd versionreports the injected version, notdev.checksums.txtcovers both debs and all four archives — the role verifies the deb against it viaget_url'schecksum:.Refs #2. Tagging
v0.1.0and the on-host install/brew installchecks follow after merge.