fix(ci): the release's health check at the viewer's origin, and the changelog's long lines #50

Merged
dawid merged 1 commit from release-fixes into main 2026-11-18 09:19:50 +00:00
Owner

Runs 156 and 157 failed.

  • 157, the v0.3.0 release: everything was built and published, and the viewer deployed. Then the health check read the address from the panel's fqdn, which is empty for the Compose app (viewer and relay; Coolify keeps a Compose app's domains per service). curl tried the host null. The check now uses WRISTMARK_ORIGIN (the repository variable) or the default origin. The site and relay answer: /healthz 200, /relay/v1/healthz ok. Nothing needs re-running.
  • 156, main's checks: the release bot wrote two commit subjects longer than 100 characters into CHANGELOG.md, and markdownlint failed. The bot writes subjects as single lines, so CHANGELOG.md now skips MD013 (a comment at its top says why). Markdownlint is clean.
Runs 156 and 157 failed. - **157, the v0.3.0 release:** everything was built and published, and the viewer deployed. Then the health check read the address from the panel's `fqdn`, which is empty for the Compose app (viewer and relay; Coolify keeps a Compose app's domains per service). curl tried the host `null`. The check now uses `WRISTMARK_ORIGIN` (the repository variable) or the default origin. The site and relay answer: `/healthz` 200, `/relay/v1/healthz` ok. Nothing needs re-running. - **156, main's checks:** the release bot wrote two commit subjects longer than 100 characters into CHANGELOG.md, and markdownlint failed. The bot writes subjects as single lines, so CHANGELOG.md now skips MD013 (a comment at its top says why). Markdownlint is clean.
fix(ci): the release's health check at the viewer's origin, and the changelog's long lines
All checks were successful
CI / checks (pull_request) Successful in 36s
CI / e2e (pull_request) Successful in 1m49s
CI / relay (pull_request) Successful in 1m30s
CI / image (pull_request) Successful in 55s
CI / android (pull_request) Successful in 2m4s
CI / watch (pull_request) Successful in 2m49s
f21d33c9c1
The deploy step read the address from the panel's fqdn, which the Compose app (viewer and
relay) leaves empty: curl got "null" and the v0.3.0 release failed after a good deployment.
It now checks WRISTMARK_ORIGIN or the default origin. The release bot writes commit subjects as
single lines, two of them over 100 characters, which failed main's checks: CHANGELOG.md skips
the line-length rule.
dawid merged commit e8feb3c374 into main 2026-11-18 09:19:50 +00:00
dawid deleted branch release-fixes 2026-11-18 09:19:50 +00:00
Sign in to join this conversation.
No description provided.