Fixed broken release tests, updated go version in docs

Author: Axodouble

CHANGELOG.md

@@ -9,7 +9,7 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 ### Added
 
 - New documented deployment methods for Tailscale and EdgeVPN, with example `docker-compose.yml` files and wrapper scripts in `docker/tailscale/` and `docker/edgevpn/`.
-- New builder command `qu builder`, which generates a standalone HTML alert-template builder
+- 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`.
 - **Custom DNS resolvers for check target resolution.** Every probe
   (HTTP / TCP / TLS / ICMP / DNS) can now bypass the host's stub
   resolver and the local cache by pointing at explicit DNS servers.
@@ -49,6 +49,38 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 - **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
 - 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.
+- 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.
+
+### Upgrade notes
+
+Existing clusters keep working with no operator action beyond rolling
+out the new binary — the three new fields (`checks[].disabled`,
+`checks[].resolvers`, `cluster.yaml.resolvers`) are all `omitempty`,
+and `alerts[].disabled` is the negation of "enabled" so unset entries
+stay enabled.
+
+Things to know during the rollout:
+
+- **Don't issue toggle or resolver edits mid-rollout.** A v0.2.x
+  daemon doesn't know `MutationSetResolvers` and will reject it
+  outright with "unknown mutation kind" if it holds master when the
+  CLI submits. Worse: if a v0.2.x master applies any
+  `MutationReplaceConfig` from the manual-edit watcher (an operator
+  saving `cluster.yaml` on an upgraded follower), it will write the
+  file back **without** the new fields — silently dropping any
+  `disabled` flags, per-check `resolvers`, or `cluster.yaml.resolvers`
+  that an upgraded node had just contributed. Finish the rolling
+  upgrade everywhere, then start using `qu check enable|disable`,
+  `qu alert enable|disable`, `qu cluster resolvers …`, and per-check
+  `--resolvers`. Pause hand-edits to `cluster.yaml` during the
+  upgrade window.
+- **Existing `dns_resolver` on DNS checks is preserved.** It now acts
+  as a legacy single-entry fallback used only when both
+  `checks[].resolvers` and `cluster.yaml.resolvers` are empty. No
+  config change required to keep current DNS-check behaviour.
+- **ICMP behaviour is unchanged when no resolver override is set.**
+  pro-bing still does its own lookup against the system resolver for
+  checks that don't configure `resolvers`.
 
 ## [v0.2.3] — 2026-05-19
 
@@ -344,4 +376,5 @@ Initial public release.
 [v0.2.0]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.2.0
 [v0.2.1]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.2.1
 [v0.2.2]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.2.2
-[v0.2.3]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.2.3
+[v0.2.3]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.2.3
+[v0.3.0]: https://git.cer.sh/axodouble/quptime/releases/tag/v0.3.0

README.md

@@ -139,7 +139,7 @@ and the daemon will replicate the edit cluster-wide.
 
 ## Build
 
-Requires Go 1.24.2 or newer.
+Requires Go 1.26.3 or newer.
 
 ```sh
 go build -o qu ./cmd/qu

docs/installation.md

@@ -82,7 +82,7 @@ What it does:
 
 ## Build from source
 
-Requires Go 1.24.2 or newer.
+Requires Go 1.26.3 or newer.
 
 ```sh
 # Either remote — Gitea is canonical, GitHub is a push-mirror.

internal/checks/resolver_test.go

@@ -3,7 +3,6 @@ package checks
 import (
 	"context"
 	"net"
-	"sync/atomic"
 	"testing"
 	"time"
 
@@ -101,25 +100,26 @@ func TestResolverFailover_DialLevel(t *testing.T) {
 	badAddr := bad.Addr().String()
 	bad.Close() // released; subsequent dials will be refused
 
-	// Working listener — we just accept and immediately close, so the
-	// dial succeeds even though it'll be useless for DNS. That's enough
-	// to prove the failover loop.
+	// Working listener — we accept once, signal via channel, then close.
+	// Signalling through a channel is deterministic; observing a counter
+	// after Dial returns races with the Accept goroutine still running.
 	good, err := net.Listen("tcp", "127.0.0.1:0")
 	if err != nil {
 		t.Fatal(err)
 	}
 	defer good.Close()
 	goodAddr := good.Addr().String()
-	var accepted atomic.Int32
+	accepted := make(chan struct{}, 1)
 	go func() {
-		for {
-			conn, err := good.Accept()
-			if err != nil {
-				return
-			}
-			accepted.Add(1)
-			conn.Close()
+		conn, err := good.Accept()
+		if err != nil {
+			return
+		}
+		select {
+		case accepted <- struct{}{}:
+		default:
 		}
+		conn.Close()
 	}()
 
 	r := resolverFor([]string{badAddr, goodAddr}, 1*time.Second)
@@ -134,8 +134,11 @@ func TestResolverFailover_DialLevel(t *testing.T) {
 		t.Fatalf("Dial fell through both: %v", err)
 	}
 	conn.Close()
-	if accepted.Load() == 0 {
-		t.Errorf("expected the working listener to be the one that accepted")
+	select {
+	case <-accepted:
+		// ok — the working listener was the one that accepted
+	case <-time.After(2 * time.Second):
+		t.Errorf("good listener did not accept within 2s; failover loop did not reach it")
 	}
 }