dockyrd 0.7.16

chore(release): ship 0.7.16 — deployments UI, railpack, connection rows

Dashboard deployment tables and trigger names, railpack install/doctor checks,
terminal and settings polish, and connection variable layout fixes.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.15

fix(proxy): valid Caddy JSON for static cache headers (0.7.15)

Wrap path-scoped headers in subroute so Caddy accepts dy_https config load.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.14

fix(proxy): recreate stale dy-proxy and add repair-edge CLI (0.7.14)

Detect plain HTTP on :443, bump proxy spec to host-v2, and load routes with
retries on startup and via dockyrd repair-edge.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.13

fix(proxy): stop edge repair from breaking TLS on dy-proxy restart

Bootstrap Caddy on :80 only; auto-repair syncs config without container
restart unless ACME HTTP is blocked.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.12

feat(edge): auto-repair HTTPS and panel edge reload (0.7.12)

Restart dy-proxy and reload routes when TLS/ACME probes fail, expose admin
API + Settings repair action, and improve terminal sandbox networking.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.11

fix(proxy): split Caddy :80/:443 for ACME HTTP-01

Separate dy_http and dy_https servers so LE challenges are not 308'd to TLS.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.10

fix(proxy): allow ACME HTTP-01 before HTTPS redirect

Disable Caddy automatic_redirects that broke certificate issuance; add
explicit HTTP→HTTPS redirect excluding /.well-known/acme-challenge/*.

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.9

v0.7.9

fix(build): pull BuildKit image; skip buildx for publish-only static …

dockyrd 0.7.8

chore(release): v0.7.8 buildkit bootstrap fix

Co-authored-by: Cursor <cursoragent@cursor.com>

dockyrd 0.7.7

fix(proxy): disable HTTP/3 to avoid QUIC errors on locked-down firewalls

Caddy now serves TLS with HTTP/1.1 and HTTP/2 only so UDP 443 is not required.

Co-authored-by: Cursor <cursoragent@cursor.com>