Orbit v0.14.4 (Preview)

What changed

Publishing one SQL project to several databases works end to end again, and three settings now behave the way the documentation describes them.

SQL configuration errors are back on a single line. The multi-line messages introduced in v0.14.2 broke out of the validation error list, so the YAML snippet offered as the fix rendered as though it were another problem. The errors still name both offending project paths and the remedy.

health_check.timeout now applies to http checks. The field was documented and honoured by tcp, but HTTP probes were capped by a fixed 5s deadline — a check configured timeout: 300ms gave up at 5.001s instead. Only configurations that explicitly set the field change behaviour, and only toward the value they asked for; omitting it still means 5s exactly as before.

An https endpoint now counts as a readiness signal. A resource publishing https alongside any second port received no inferred probe, and orbit doctor warned that Orbit "cannot infer when it is ready" — about a configuration v0.14.2 had just documented. Resources whose only endpoint is TLS now get the same TCP readiness check an http endpoint would.

Publish errors stop blaming the wrong file. When a build produced no usable dacpac, the error asserted the build "wrote X instead" and pointed at a <SqlTargetName> override. The build directory also holds a project's <ProjectReference> dacpacs, so an ordinary build failure named a dependency as the culprit and sent you hunting for an override that did not exist.

Documentation corrections in both locales: tls_skip_verify follows redirects, including to another host; health_check.timeout bounds http and tcp probes while exec is bounded by the surrounding operation and a log wait defaults to 60s; a probe that times out costs its timeout rather than its interval, so a large timeout stretches the startup budget toward retries × timeout; and readiness inference accepts an https alias, not only http.

This release replaces v0.14.3, which was withdrawn shortly after publication. It carries the same fixes.

Why it matters

Every item here is a case where Orbit's own documentation described behaviour the code did not deliver. A databases: project could not publish at all, a configured HTTP timeout was silently discarded, and a TLS-only service was told Orbit could not tell when it was ready. Each one cost time in the place where trust matters most — the error message or the setting you reach for when something is already wrong.

The release also closes the gap that let the publish defect ship: the live SQL Server gate now names its test project and target database differently, so a build artifact resolved under the wrong name fails the release instead of reaching users.