Open taherkk opened 1 month ago
Hi @taherkk, thanks for opening this issue!
This version contained a major version upgrade in goreleaser. Please follow the guidance in goreleaser's release notes to upgrade: https://github.com/goreleaser/goreleaser/releases/tag/v2.0.0
Otherwise you can pin your repo to use v4.1.0 of this workflow if you're not ready to upgrade.
Hi @deniseyu,
Can you please share a link to the tag v4.1.0 because I can't find it in this repo.
@taherkk sorry, typo - I meant v4.0.1! https://github.com/hashicorp/ghaction-terraform-provider-release/releases/tag/v4.0.1
@deniseyu ,
That wouldn't help since it too uses v5.0.0 of the goreleaser-action, since it uses the latest tag for goreleaser and will end up using v2 of goreleaser, which is analogus to the current situation where we are using v3 of the this workflow and it is using v2 of goreleaser while it should be using v1.
I think I wasn't clear enough in my first comment. When I said that the community.yml should use v5.1.0 of goreleaser-action, I meant that v4 and below of this workflow should be using v5.1.0 to keep using v1 of the goreleaser while v5 of this workflow uses the v2 of goreleaser that has breaking changes.
Currently the v3 of community.yml uses v5.0.0 of goreleaser-action which uses latest version of goreleaser. The current release of goreleaser is v6 which has breaking changes and it is causing issues with our github workflows.
community.yml should be using v5.1.0 of goreleaser-action which uses v1 of the goreleaser package and not the latest.