v0.17.6: Refresh the release toolchain

What's Changed

• Release builds now use Go 1.26.10, closing the standard-library advisories reported by govulncheck.
• The .deb/.rpm packaging step no longer depends on the Go version pinned by the tag.
• No app behavior, IPC or configuration changes; existing profiles and settings keep working.

Full Changelog: v0.17.5...v0.17.6

v0.17.4: Update the Xray runtime pin and client toolchain

What's Changed

• Xray-core is now pinned to v26.10.31; the previous pin had no upstream release, so fresh installs and runtime updates could not download the engine.
• whoisthat doctor recognises the new pinned runtime.
• The daemon uses refreshed Go dependencies (miekg/dns, grpc, x/net, x/sys).
• The client uses refreshed Rust dependencies (tokio, serde, crossterm 0.29, toml 1.1, arboard, log).
• The client now builds with Rust edition 2024 and requires Rust 1.88 or newer.

Full Changelog: v0.17.3...v0.17.4

v0.17.3: Route JSON manual proxy rules through the provider default

What's Changed

• Manual proxy rules in JSON subscriptions now follow the provider's first catch-all balancer or outbound instead of a random pick over every proxy outbound.
• The generated fallback balancer no longer selects chained dialerProxy outbounds.
• whoisthat route list no longer reports manual rules as shadowed for JSON subscription groups.

Full Changelog: v0.17.2...v0.17.3

core-v0.4.5: Refresh dependencies and Xray mirror fallback

Full Changelog: core-v0.4.4...core-v0.4.5

core-v0.4.4: Update the Xray runtime pin and client toolchain

What's Changed

• build(deps): bump the actions group with 6 updates by @dependabot[bot] in #2
• build(deps): bump the go group in /core/core with 4 updates by @dependabot[bot] in #1
• build(deps): bump crossterm from 0.28.1 to 0.29.0 by @dependabot[bot] in #5
• build(deps): bump toml from 0.8.23 to 1.1.8+spec-1.1.0 by @dependabot[bot] in #4
• build(deps): bump the rust group across 1 directory with 5 updates by @dependabot[bot] in #3

New Contributors

• @dependabot[bot] made their first contribution in #2

Full Changelog: core-v0.4.3...core-v0.4.4

core-v0.4.3: Route JSON manual proxy rules through the provider default

Full Changelog: core-v0.4.2...core-v0.4.3

v0.17.2: Add provider-driven subscription auto-update and move installs to /usr/bin

What's Changed

• Subscriptions refresh automatically using the provider's profile-update-interval (HTTP header or body directive), including missed updates after a long shutdown.
• Background refreshes store new profiles without running latency tests or reconfiguring a live DNS/routing/TUN session; failures keep the old profiles and retry with exponential backoff.
• Add a per-subscription auto-update toggle and optional manual interval in Edit Group, plus sub auto / sub interval CLI commands and an AUTO column in sub list.
• Raise the IPC protocol to 4; the TUI restarts an older core once after upgrading.
• Install binaries to /usr/bin from make install and install.sh; legacy /usr/local/bin copies are removed automatically.

Full Changelog: v0.17.1...v0.17.2

v0.17.1: Add log search, filtering, clearing and diagnostics

What's Changed

• The Logs tab now has an incremental search (/) and a confirmed clear action (c) for the current log source.
• whoisthat logs gained --source core|tui, --since (absolute time, 30m/2h/3d, today, yesterday) and --grep (case-insensitive substring); filters combine with --level and work with --follow.
• whoisthat logs clear --source core|tui|all --yes truncates active logs in place and removes rotated backups, including core-crash.log for the core source.
• RUST_LOG or WHOISTHAT_LOG_LEVEL now enables the TUI file log and applies the level to the core for one session without changing config.toml.
• whoisthat doctor --logs reports log paths, permissions, rotation state, the crash log and the last error lines.

Full Changelog: v0.17.0...v0.17.1

core-v0.4.2: Add provider-driven subscription auto-update and move installs to /usr/bin

Full Changelog: core-v0.4.1...core-v0.4.2

v0.17.0: Add JSON subscriptions with per-server provider routing

Package revision 2

• JSON subscriptions that ship custom geoip.dat/geosite.dat now connect even when manual rules use global codes such as geoip:ru or geosite:category-ru.
• The provider dataset and the whoisthat-wide dataset are exposed side by side at runtime, so provider rules and manual rules both resolve in the same Xray process.
• Existing JSON profiles need no re-download: the global assets are linked on the next connect.

What's Changed

• JSON subscriptions: u now prefers <subscription>/json and imports one full Xray configuration per server, so provider-owned routing, balancers and DNS work out of the box.
• Provider JSON routing is immutable and replaced on every refresh; manual rules from the Routing tab still apply and take priority. JSON groups are marked [JSON] in the TUI and the routing-mode/Happ selectors are locked.
• Subscription groups are named after the provider (profile-title, then URL host); manual renames survive refreshes.
• Damaged settings and profile files are no longer overwritten with defaults: every readable value is recovered and a one-key restore is offered.
• Logging is unified: dated [LEVEL] lines, core crash capture, a terminal-restoring TUI panic hook, live core log level over IPC, CLI log tailing and bounded rotation.
• Exclude-mode split tunneling re-asserts its physical policy route, and whoisthat doctor reports when that route is missing.
• Running the test suite no longer overwrites the live configuration.

Full Changelog: v0.16.0...v0.17.0