Server 1.194.5 fixes a bug in project deployment readiness checks.
- Kura server activations now tolerate public HTTPS endpoints that aren’t reachable yet. Previously, a conflicting option in the readiness probe could raise an internal error and crash the deployment tick instead of marking the endpoint as not ready. The probe no longer passes an explicit Finch pool alongside custom connection options, and it disables extra retries so the reconciler loop handles the retry schedule. If the public endpoint isn’t ready due to DNS, TLS, or load-balancer propagation, activation returns a readiness error and the next reconciliation tick retries.
The Docker image for this release is ghcr.io/tuist/tuist:1.194.5.