-
Notifications
You must be signed in to change notification settings - Fork 211
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
Feature request: Tagged releases #383
Comments
/cc @apelisse |
Yeah, we would need to think of a strategy for that. I agree we haven't done great with that. Do you have any specific requirements? |
not sure if the question is for me, but I don't have any specific requirements, just any kind of versioning will work |
I am trying to use helm SDK to install helm chart on my eks cluster . however I see its getting difficult to manage the dependencies with what version to be used go 1.20 replace example.com/pkg => ../pkg require (
) require ( require (
) k8s.io/client-go/applyconfigurations/meta/v1../../../../pkg/mod/k8s.io/[email protected]/applyconfigurations/meta/v1/unstructured.go:64:38: cannot use doc (variable of type *"github.com/googleapis/gnostic/openapiv2".Document) as *"github.com/google/gnostic/openapiv2".Document value in argument to proto.NewOpenAPIData Compilation finished with exit code 1 Can some help with the right version to be user |
Having tags somewhat corresponding to Kubernetes releases would be really nice. We bump patch versions of k8s dependencies automatically (with Renovate), but minor versions manually. At the moment we have to exclude kube-openapi from all automatic updates. |
@Jefftree We have that discussion in another issue? Can we close this one and link to the other one? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
👍 for the idea to have tagged releases. This bit me after bump to 1.30 and then I realized that kubernetes/code-generator@9620d16 removed openapi-gen where it was hosted in code-generator which does have tags for releases. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
We use dependabot to keep our dependencies up to date and it seems like it's struggling with dependencies that don't have tags/releases.
Would it be possible to start creating tags? Thanks!
The text was updated successfully, but these errors were encountered: