Kustomize stuck on outdated goreleaser version

[KnVerey]

Kustomize is currently relying on goreleaser's --skip-validate flag to ignore the fact that our tags are not pure semver (because they have module prefixes). That flag was deprecated long ago, and removed in v0.180.0 in Sept 2021. Multi-module repos like our are supposed to move to the "monorepo" feature, which requires a paid Pro license.

#4571 manually installs v0.179.0 into a container with Go 1.18 so that we aren't stuck building with the old Go version the corresponding official goreleaser container bundles. But this is still a risk for us in the medium to long term.

Potential options:

• Pay for a Pro license?
• Stop using goreleaser? (what does the rest of the project do?)

FYI @natasha41575 this seems pretty important and may be high effort

[k8s-ci-robot]

@KnVerey: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jzelinskie]

I think you should just purchase goreleaser and support @caarlos0

The CNCF provides budget for things like this. I believe you just need to use the service desk.

[caarlos0]

I'm also happy to give a discount as it is for OSS :)

[pre]

If there’s budget, I don’t understand the urge to ”not pay” for useful tools.

The cumulative cost for finding an alternative is of course zero if the voluntary work doesn’t cost anything (except if someone performs this as part of their salary job ..)

I doubt the license cost is that much for an open source project, especially if there’s support from the author.

[koba1t]

I think this issue was resolved with merge for #5239.
/close

[k8s-ci-robot]

@koba1t: Closing this issue.

In response to this:

I think this issue was resolved with merge for #5239.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.