feat(ci): use docker bake to build binaries

[nlevee]

Fix #377

[mckaygerhard]

Hi @nlevee may you enable squashig of the PR ? also release will only work in lasted linuxes and most of the non expert users will not understand the complexity of the workflow of a web service program

[nlevee]

Hi @nlevee may you enable squashig of the PR ? also release will only work in lasted linuxes and most of the non expert users will not understand the complexity of the workflow of a web service program

Hi,
Ho do I enable squashing ?

Build is now working on each tag prefixed by "v*". It create a release automatically.
I think It's more simple to find the binary in release page instead of action summary (for artifacts), don't you ?

[varbhat]

Hey, I had already valuated goreleaser before but for some reasons didn't use it(some features were under pro license, it did too much instead of doing minimum required things, etc.).More than these, it was difficult to integrate with musl builder that i was using. So i went no-tools route.

Have you looked into https://github.com/arp242/gogo-release ? It was better imo.

[nlevee]

Hey, I had already valuated goreleaser before but for some reasons didn't use it(some features were under pro license, it did too much instead of doing minimum required things, etc.).More than these, it was difficult to integrate with musl builder that i was using. So i went no-tools route.

Have you looked into https://github.com/arp242/gogo-release ? It was better imo.

I totaly agree, I forgot to change the PR name, i don't use goreleaser anymore for the same reason you had before. I use docker because it work well and permit to build and publish with a single solution.

[nlevee]

@varbhat do you have review on this PR ?