-
|
Hello, After some debugging I found out that https://github.com/goreleaser/goreleaser/blob/main/internal/pipe/blob/upload.go#L155 Types "Binary" and "UploadableBinary" have the same string representation, but are different. If I add the "Binary" type to the filter my upload works. Is it working as intended? If so, how could I change the build config to generate an "UploadableBinary"? I used version 2.10.2, and my config looks like: version: 2
before:
hooks:
- go mod download
builds:
- env:
- CGO_ENABLED=0
...
goos:
- linux
goarch:
- amd64
blobs:
- provider: s3
bucket: arts
endpoint: https://s3.... Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Also, this is a local test. I wonder if when I publish to github the artifact type will be an "UploadbleBinary" and it will work. |
Beta Was this translation helpful? Give feedback.
-
|
Hi!
archives:
- formats: [ binary ]this should fix it I think :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi Carlos, this does the trick, thanks! I also added this snippet to my local test config: release:
disable: trueto avoid publishing artifacts to github. |
Beta Was this translation helpful? Give feedback.
-
|
cool! FWIW I tried to make that a tad clearer in the docs, so thanks for letting me know this was confusing/unclear 🙏🏻 |
Beta Was this translation helpful? Give feedback.
-
|
I should have started by mentioning that my intent was to do a local test to check if S3 upload was working. |
Beta Was this translation helpful? Give feedback.
Hi!
UploadableBinaryis made by the archive config:this should fix it I think :)