Skip to content

fix: build the acor package, not main.go alone, in the release #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skyoo2003 merged 1 commit into from
Sep 6, 2026
Merged

fix: build the acor package, not main.go alone, in the release #247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .goreleaser.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,12 @@ before:
builds:
- id: acor
binary: acor
main: cmd/acor/main.go
# The package, not `cmd/acor/main.go`. A file path compiles that file alone as
# `command-line-arguments`, excluding its siblings in the same package — which
# held only while `cmd/acor` was one file, and stopped holding the moment
# `dictionary.go` arrived, failing the v1.6.0 tag build. Naming the package
# builds what `make build` builds, so that target now gates this one.
main: ./cmd/acor
# Stamps `acor version`. Without this a release binary reports its "dev"
# default, so a bug report would not say which release it came from.
# .Version, not .Tag: it is the unprefixed number the brew formula, the OCI
Expand Down