prefer goreleaser nfpm to fpm #154
Merged
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.
Replace the
fpm
gem for building .deb packages with thenfpm
library embedded within goreleaser.Modify the Makefile to prefer invoking
goreleaser
for all artifacts. Per the.github/workflows/release.yaml
workflow: this Makefile isn't used during the release process, it's inherited cruft.Moving this logic from the
Makefile
, which we don't use, togoreleaser
, which we do use, means the next tagged release will have a.deb
attached with provenance.This PR also upgrades the dependencies specified in
dev.yml
: ruby and golang to fresher versions.Testing Instructions
make deb
will producedist/*.deb
.git rev-parse
instead of theVERSION
file(?), and I don't want to do that.Related