release: v1.6.4

The installer's DNS-port check warned that xray was blocking xray's own DNS
port. Shipped in 1.6.2 and seen on every upgrade of a healthy box since:
the check catches something squatting on UDP/5353, and on an upgrade the
process holding it is the one that is supposed to.

Tagged rather than left on master so the fix is traceable to a version —
the installer is fetched from master and was already correct, but a box
reporting 1.6.3 gives no way to tell whether it has this.

Author: DaveBugg

CHANGELOG.md

@@ -4,6 +4,18 @@ All notable user-facing changes to PiTun. Full per-release detail lives in the
 [GitHub Releases](https://github.com/DaveBugg/PiTun/releases); this file is the
 committed summary.
 
+## v1.6.4 — 2026-08-15
+
+### Fixed
+
+- **The installer warned that xray was blocking xray's own DNS port.** The
+  check exists to catch something squatting on UDP/5353, which PiTun's DNS
+  needs. On an upgrade the process holding it is xray — it *is* that DNS — so
+  every operator of a healthy box was told their DNS would not start, with
+  the pid of the process already serving it offered as evidence. It now
+  ignores xray and still reports anything else, including something listening
+  alongside it.
+
 ## v1.6.3 — 2026-08-14
 
 **Country flags on nodes actually appear now** — and look the same on every

backend/app/config.py

@@ -5,7 +5,7 @@
 # OpenAPI metadata, `/health` response, and `/system/status` so the
 # frontend can display it next to the xray version. Bump this on each
 # release — frontend keeps its own version in `frontend/package.json`.
-APP_VERSION = "1.6.3"
+APP_VERSION = "1.6.4"
 
 
 class Settings(BaseSettings):

frontend/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pitun-frontend",
   "private": true,
-  "version": "1.6.3",
+  "version": "1.6.4",
   "license": "BSD-3-Clause",
   "type": "module",
   "scripts": {