-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Any reason to change the release tag scheme? #5454
Comments
@jchauncey apologies for the change. This is required due to the migration of the helm chart to this repository and the need to release both artifacts from this repository. |
Sounds good! |
Just curious @aledbf, so moving forward, the associated helm chart won't be anymore here: https://github.com/helm/charts/tree/master/stable/nginx-ingress but will be here now: https://github.com/kubernetes/ingress-nginx/tree/master/charts/ingress-nginx, correct? So it won't appear anymore in https://hub.helm.sh/charts/stable/nginx-ingress moving forward? |
Correct.
The stable repository is being deprecated. Please check https://github.com/helm/charts/issues/21103 |
Go it, thanks!
Didn't know/notice that (but makes a lot of sense to track individually the helm chart release for example), thanks for the info! |
PS @jchauncey @mathieu-benoit there's now a documented migration path from |
It went from
nginx-<semver>
tocontroller-<semver>
. This broke some automation we have around rebuilding the project for internal releases so just want to make sure if this was intentional or an accident?The text was updated successfully, but these errors were encountered: