-
Hello, I've successfully used gorelease to build my project, and in the /dist folder, I can see binaries and archives containing binaries for all requested goos. However, when attempting to release to GitHub, only the source archives are uploaded, and the binaries seem to be missing. I suspect that there might be a configuration setting I overlooked: version: 1
before:
hooks:
# You may remove this if you don't use go modules.
- go mod tidy
report_sizes: true
builds:
- main: ./app/docops
id: "docops"
binary: "docops"
env:
- CGO_ENABLED=0
goos:
- linux
- windows
- darwin
goarch:
- amd64
- arm64
ignore:
- goos: windows
goarch: arm64
archives:
- builds:
- docops
format: tar.gz
# this name template makes the OS and Arch compatible with the results of `uname`.
name_template: >-
{{ .ProjectName }}_
{{- title .Os }}_
{{- if eq .Arch "amd64" }}x86_64
{{- else if eq .Arch "386" }}i386
{{- else }}{{ .Arch }}{{ end }}
{{- if .Arm }}v{{ .Arm }}{{ end }}
# use zip for windows archives
format_overrides:
- goos: windows
format: zip
files:
- docops*.md
release:
ids:
- docops
draft: false
prerelease: auto
mode: keep-existing
disable: false
skip_upload: false
changelog:
use: git
sort: asc
groups:
- title: Features
regexp: '^.*?feat(\([[:word:]]+\))??!?:.+$'
order: 0
- title: "Bug fixes"
regexp: '^.*?bug(\([[:word:]]+\))??!?:.+$'
order: 1
- title: Others
order: 999
filters:
exclude:
- "^docs:"
- "^test:"
- "Merge" Any assistance on resolving this matter would be greatly appreciated. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
if you only have one build, one archive, etc, no need to be setting The source archives you see are added by github, not goreleaser. |
Beta Was this translation helpful? Give feedback.
if you only have one build, one archive, etc, no need to be setting
id
andids
, remove them, your release configuration is yielding no artifacts to upload.The source archives you see are added by github, not goreleaser.