-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kustomize stuck on outdated goreleaser version #4542
Comments
@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 The 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. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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. |
I'm also happy to give a discount as it is for OSS :) |
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. |
I think this issue was resolved with merge for #5239. |
@koba1t: Closing this issue. In response to this:
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. |
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:
FYI @natasha41575 this seems pretty important and may be high effort
The text was updated successfully, but these errors were encountered: