Skip to content

Unexpected different behavior between v0.123 and v0.124 #1294

@gianarb

Description

@gianarb

Describe the bug

I used to run Gorelaser in a GitHub action with version latest. Recently (I discovered it today), it stoped working with the error:

   • DOCKER IMAGES            
   ⨯ release failed after 167.34s error=0 binaries match docker definition: [kprofefe]: linux_amd64_, should be 1
##[error]The process '/home/runner/work/_temp/72c914c2-6539-4778-8a04-ae687d59d195/goreleaser' failed with exit code 1
##[error]Node run failed with exit code 1

But as you can see here the last time I ran a release it worked:

https://github.com/profefe/kube-profefe/runs/372635928

Looking at the goreleaser version download with latest it was v0.123 at that time.

I saw that ~17h ago latest changed to a newest version, this version causes the failure. I had to pin v0.123

To Reproduce

You can verify it cloning my repository:

git clone git@github.com:profefe/kube-profefe.git
# This works
docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -it -v $PWD:/app -w /app goreleaser/goreleaser:v0.123 release --rm-dist --snapshot --skip-publish

# This fails
docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -it -v $PWD:/app -w /app goreleaser/goreleaser:latest release --rm-dist --snapshot --skip-publish

Expected behavior

I do not expect to change the configuration file when updating Goreleaser.

Environment (please complete the following information):

See GitHub action. I used my laptop to reproduce it locally

$ uname -a
Linux gianarb 5.2.14-arch2-1-ARCH #1 SMP PREEMPT Thu Sep 12 10:42:38 UTC 2019 x86_64 GNU/Linux

Additional context

Thanks, I love Goreleaser!! ❤️

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions