-
v0.0.19
StableGates / frontend (push) Successful in 2m3sGates / test (push) Successful in 2m33sGates / test-aarch64 (push) Successful in 8m14sGates / package (push) Successful in 52sGates / container (push) Successful in 14sCI / gates (push) Successful in 12m0sRelease / guard (push) Successful in 33sGates / frontend (push) Successful in 2m36sGates / test (push) Successful in 3m47sGates / test-aarch64 (push) Successful in 7m24sGates / package (push) Successful in 50sGates / container (push) Successful in 15sRelease / gates (push) Successful in 12m19sRelease / publish (push) Successful in 6m37sreleased this
2026-09-12 09:14:36 +00:00 | 4 commits to master since this releaseChanged
- A failed blocklist download says why. The warning line and the Diagnostics event detail now carry the phase that failed, the concrete cause behind the classification (a reset connection, a truncated chunk, a TLS handshake fault), the HTTP status if a head arrived, the bytes received, and the elapsed time. The separate
http statuswarning is folded into that line. Same one line per failed source per pass as before.
Artifacts
4af595f259b225671e54186e00eb6574c6f0180f212f1fe9b8955d6b6b74b028 nxdns-0.0.19-x86_64-linux-musl.tar.gz b0d223b272794cf469484ff00edc1bd23ee5632c8c5c23ccc1cec802fe6ccb7b nxdns-0.0.19-aarch64-linux-musl.tar.gz b1afe29eed90b2e87e7fd603ea8e6e6478d96946861151efbd3275adf0ff4fe3 IMAGE-DIGEST.txtgit.mial.net/mokhtar/nxdns:0.0.19@sha256:b80023379b012db3898d78f716a5e6c6967459416252f528cc207cffae44b0e5Commits since v0.0.18
f4562ca filter: skip the read-only directory test as root, ci's runner ignores mode bits 250bdca build: bump version to 0.0.19 63f4f96 changelog: date the 0.0.19 section 5215819 filter: a failed blocklist download names its phase, cause, status, bytes and elapsed time bf79a22 docs: renovate's nix manager does not bump a tag ref; the regex manager recipe that doesDownloads
- A failed blocklist download says why. The warning line and the Diagnostics event detail now carry the phase that failed, the concrete cause behind the classification (a reset connection, a truncated chunk, a TLS handshake fault), the HTTP status if a head arrived, the bytes received, and the elapsed time. The separate