You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+80-1Lines changed: 80 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,84 @@ All notable changes to this project are documented here. The format
4
4
follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
5
5
this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
7
+
## [v0.3.0] — 2026-05-25
8
+
9
+
### Added
10
+
11
+
- New documented deployment methods for Tailscale and EdgeVPN, with example `docker-compose.yml` files and wrapper scripts in `docker/tailscale/` and `docker/edgevpn/`.
12
+
- New builder command `qu builder`, which generates a standalone HTML alert-template builder. The builder ships with a rich expression palette (more logic operators, comparison helpers, and `with` blocks) so you can author multi-branch subject / body templates and copy the rendered Go `text/template` directly into `qu alert add … --body-file`.
13
+
-**Custom DNS resolvers for check target resolution.** Every probe
14
+
(HTTP / TCP / TLS / ICMP / DNS) can now bypass the host's stub
15
+
resolver and the local cache by pointing at explicit DNS servers.
16
+
Two new fields, both `omitempty`:
17
+
-`cluster.yaml.resolvers` — cluster-wide default list, edited via
-`checks[].resolvers` — per-check override, set via the new
20
+
`--resolvers` flag on `qu check add <type>` and `qu check edit`.
21
+
22
+
Lookup precedence on each probe: per-check → cluster default →
23
+
(DNS checks only) legacy `dns_resolver` → host system resolver.
24
+
Each entry is `host[:port]` — a bare host gets `:53` appended at
25
+
use time. Lists are tried in order with **connection-level
26
+
failover**, so `[1.1.1.1, 1.0.0.1]` rolls over to Cloudflare's
27
+
secondary when the primary is unreachable. Literal IP targets
28
+
skip the resolver entirely. ICMP only consults the resolver list
29
+
when an override is configured; existing ICMP checks with no
30
+
override behave unchanged.
31
+
-**Pause checks and alerts without deleting them.** Both `Check` and
32
+
`Alert` carry a new `disabled` (yaml `disabled,omitempty`) field.
33
+
Disabled checks are skipped by the scheduler — their workers are
34
+
cancelled on the next reconcile pass — so no probes run and the
35
+
aggregator stops receiving fresh results. Disabled alerts are
36
+
filtered out by `EffectiveAlertsFor` before the dispatcher sees
37
+
them, so they neither fire on transitions nor count toward the
38
+
`default: true` attachment set. Toggle from the CLI with
39
+
`qu check enable|disable <id-or-name>` and
40
+
`qu alert enable|disable <id-or-name>`; from the TUI, `x` on the
41
+
Checks or Alerts tab. `qu check list` / `qu status` mark disabled
42
+
checks with `(disabled)` in the STATE column, `qu alert list`
43
+
gained an `ENABLED` column, and the TUI Checks / Alerts tabs gained
44
+
an `ON` column. The field is stored as the negation of "enabled"
45
+
so the zero value of new and existing entries stays enabled — no
46
+
migration needed.
47
+
48
+
### Changed
49
+
50
+
-**TUI modals now scroll** when a form is taller than the terminal (e.g. the SMTP "Add alert" form on a short window). The view auto-centres on the focused field and shows `↑/↓ N more` indicators when content is clipped above or below. #24
51
+
- TUI main page no longer overflows on very short terminals — the body shrinks all the way down to a single row instead of pinning to 5.
52
+
- Release workflows on both Gitea and GitHub now treat `-beta` tags as pre-releases in addition to `-rc`, so a `v0.3.0-beta1` push lands as a pre-release without manual flagging.
53
+
54
+
### Upgrade notes
55
+
56
+
Existing clusters keep working with no operator action beyond rolling
57
+
out the new binary — the three new fields (`checks[].disabled`,
58
+
`checks[].resolvers`, `cluster.yaml.resolvers`) are all `omitempty`,
59
+
and `alerts[].disabled` is the negation of "enabled" so unset entries
60
+
stay enabled.
61
+
62
+
Things to know during the rollout:
63
+
64
+
-**Don't issue toggle or resolver edits mid-rollout.** A v0.2.x
65
+
daemon doesn't know `MutationSetResolvers` and will reject it
66
+
outright with "unknown mutation kind" if it holds master when the
67
+
CLI submits. Worse: if a v0.2.x master applies any
68
+
`MutationReplaceConfig` from the manual-edit watcher (an operator
69
+
saving `cluster.yaml` on an upgraded follower), it will write the
70
+
file back **without** the new fields — silently dropping any
71
+
`disabled` flags, per-check `resolvers`, or `cluster.yaml.resolvers`
72
+
that an upgraded node had just contributed. Finish the rolling
73
+
upgrade everywhere, then start using `qu check enable|disable`,
74
+
`qu alert enable|disable`, `qu cluster resolvers …`, and per-check
75
+
`--resolvers`. Pause hand-edits to `cluster.yaml` during the
76
+
upgrade window.
77
+
-**Existing `dns_resolver` on DNS checks is preserved.** It now acts
78
+
as a legacy single-entry fallback used only when both
79
+
`checks[].resolvers` and `cluster.yaml.resolvers` are empty. No
80
+
config change required to keep current DNS-check behaviour.
81
+
-**ICMP behaviour is unchanged when no resolver override is set.**
82
+
pro-bing still does its own lookup against the system resolver for
0 commit comments