cc @sindresorhus.com, this includes a bunch of packages in the chalk org (including chalk itself).

Just wanted to say that I appreciate all the work that went into RSC and owner stacks, I really enjoy using them!

Everything is working again and was caused by me manually enabling the proxy protocol 2 years ago instead of doing this in code.

Thanks to everyone helping me in the GW2 Dev Community Discord ❤️

Also if you are a maintainer of anything, please follow semver if you say you are using semver 🤡

- This leads me to a ingress-nginx breaking change released as a minor version now requiring `allow-snippet-annotations: "true"`

- Additionally `annotations-risk-level: Critical` is required in ingress-nginx 1.12.0

- This makes the snippets work again

- I enable use-proxy-protocol again

- I update to the latest ingress-nginx again (still without the proxy protocol). Some ingresses are working, but others are breaking now...

- I figure out that only ingresses using configuration-snippet annotations are broken

- Removing the annotation makes all ingresses work for now

- As ingress-nginx and the hetzner load balancer use a different protocol, I get weird error messages like ERR_SSL_PROTOCOL_ERROR, which cause me to investigate cert-manager first. nginx logs are not really useful

- I finally figure out that disabling the proxy protocol fixes things temporarily

- Updating removes my manual config map changes and everything breaks, because I'm still using the proxy protocol (and snippet annotations, important later), which ingress-nginx can't handle

- I roll back the update, but since my manual config map change was not managed by helm, it's still broken

- Some day I manually added `use-proxy-protocol: "true"` to the ingress-nginx config map and enabled the proxy protocol in the hetzner load balancer

- Because of the recent CVEs I decide to update ingress-nginx, which I haven't done in 2 years (running 1.6.4 (helm chart 4.5.2)) to 1.12.1 (4.12.1)