Move back to latest for goreleaser

[mx-psi]

Because of goreleaser/goreleaser/issues/5138, CI is currently broken when using goreleaser v2.3.0+.

#667 fixes this temporarily for the next release

[jade-guiton-dd]

Are we sure we want to move back to latest instead of upgrading the version periodically? Manually upgrading would prevent the CI unexpectedly breaking on main like it did twice already.

[mx-psi]

Could we automate the bumping? For other stuff like Github Actions we use dependabot/renovate bot, but here I don't think there is an equivalent tool that is ready for this. Maybe we can ask upstream on the goreleaser repositories for advice?

[mowies]

it would be possible with renovate i believe. maybe with some additional config to cover all occurrences, but it should be possible

[mx-psi]

@mowies Do you have any links/examples explaining how this would be done with renovate?

[mowies]

Something like this should work with renovate. It's a custom regex manager that matches the goreleaser action's input for the version. It could probably be done a little nicer and more resilient but it should work I think.

    {
      "fileMatch": [
        "(^|\\/).github\\/.*\\.ya?ml$"
      ],
      "matchStrings": [
        "goreleaser\\/goreleaser-action@[\\S\\s]+version: (?<currentValue>.*?)$"
      ],
      "depName": "github.com/goreleaser/goreleaser",
      "datasourceTemplate": "github-releases"
    }

[mowies]

@mx-psi if you could take care of setting up renovate in this repo (or tell me what to do), then i'd be happy to contribute the needed config changes :)

[mx-psi]

I believe you will have to file an issue similar to this one: open-telemetry/community/issues/1792 but for this repository. I am happy to voice my support in such an issue.

[mowies]

Cool! I filed the issue: open-telemetry/community#2403

[mowies]

i will work on this when the renovate PR is merged, pls assign to me :)

[mx-psi]

Done!

[mowies]

PR is open for this: #728

[mowies]

seems like the regex I added still has some issues. I'll do a follow up PR

[mowies]

@mx-psi maybe this PR fixes it: #733