Repository navigation
Releases
waX VPN v1.0.29
waX VPN v1.0.29
Show configured routes in the expanded loaded-config summary reveals up to 64
AllowedIPs entries, labeled by peer position, in a bounded 128px scroll area.
Extra entries are counted explicitly. This is the loaded config before split
exclusions, not current routes, IP membership, reachability or leak protection.
Keys and endpoints are excluded. The view opens only on request and can be
collapsed. Copy summary retains its existing allowlist and does not copy this
route preview. No files, settings or networking behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests: 55 passed, one manual network test ignored. New coverage checks
ordered peer positions, IPv4/IPv6, empty routes, key/endpoint exclusion and the
64-entry bound with an explicit remainder count. Build and PowerShell parser
passed. Actual local screenshot inspected for readable limits and one route.
Preview https://github.com/vio137/wax-vpn/actions/runs/43185438033
source c47e21be3676d7413c0988969a9b5fa5b734eb2a: all three execution jobs
passed. Actual Windows proof checked explicit route expand/collapse, the loaded
CIDR and peer position, configured-only limits and unchanged local state without
an adapter. Prior search/clipboard/cache reload/profile/demo/recovery/installer
checks passed. Configured-route and installed-GUI pixels inspected. The 64-entry
bound and IPv6 routes are unit-tested, not Windows UI-fixture checked.
Stable https://github.com/vio137/wax-vpn/actions/runs/43187434822
source 76e27441f79b5052b7c4b1cf798e210a58ad699a: all four jobs passed.
Actual stable results read: route expand/collapse and limits, unchanged local
state, prior search/clipboard/cache/profile checks, demo tunnel ping, recovery
in 4 seconds, disabled recovery in 48 samples over 12 seconds, original HWND/PID
restore and quit, and fresh install/upgrade/uninstall/process scope.
336 console samples saw no window; shorter flashes could be missed. Configured
route and installed-GUI pixels inspected.
Published installer downloaded and matched the published SHA-256:
cf198d7dddffe626ff91ad7bc58a77d8494e857c0cd13fa201121d74fcaf0688
(11,772,993 bytes).
https://github.com/vio137/wax-vpn/releases/tag/v1.0.29
Optional layout-state captures remain unverified because their separate harness
host lacks System.Drawing; the CI-only fix remains deferred for workflow
permissions. This candidate does not change the workflow.
Design review
Keep the existing graphite card and text hierarchy. A small explicit action
reveals factual route content without decorative badges or motion; the route
list height is capped at 128px. Design reference: Unslop by Damir Sokolovsky
(@heydamir), CC BY 4.0, used as a review rubric.
Contributors
Assets 4
waX VPN v1.0.28
waX VPN v1.0.28
Local profile search now matches configured interface addresses, DNS addresses
and peer route CIDRs, alongside names and endpoints. All words must match one
profile. Matching is literal case-insensitive text, not CIDR membership, live
routing or a connection check. Both Profiles and the Connect quick picker use
the same cache. Key material is never indexed. The cache follows existing
successful-reload and ranking invalidation. No files, settings or network
behavior change just by searching.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests: 54 passed, one manual network test ignored. New coverage checks
IPv4/IPv6 addresses, DNS, route CIDRs, multi-field queries, literal misses,
key exclusion and reload invalidation. Build and PowerShell syntax passed.
Preview https://github.com/vio137/wax-vpn/actions/runs/43181431620
source bc6194865a07945a282c0e0e3aaa851d6b96aa58: all three execution jobs
passed. Actual Windows evidence checked address/route queries in Profiles and
the quick picker, unique matches, literal misses and unchanged local state with
no adapter. Prior profile/summary clipboard/cache reload, demo, recovery and
installer checks passed. Both search views and installed GUI pixels inspected.
Stable https://github.com/vio137/wax-vpn/actions/runs/43183513122
source 3cd93209b111931156e4446f35811c7c18aa156f: all four jobs passed.
Actual stable evidence read: both configured-IP search fixtures and literal
misses, unchanged state, prior clipboard/cache/profile checks, demo tunnel ping,
4-second recovery, disabled recovery in 48 samples over 12 seconds, original
HWND/PID restore and quit, and fresh install/upgrade/uninstall/process scope.
334 console samples saw no window; shorter flashes could be missed. Both search
views and installed-GUI pixels inspected. DNS/IPv6 search cases are locally
tested, not separately checked by the Windows UI fixture.
Published installer downloaded and matched the published SHA-256:
d7a285e75a4efd67e4c84742a8fa6cd6536aceb1f06db613dffd2e95c4b9c9b2
(11,770,024 bytes).
https://github.com/vio137/wax-vpn/releases/tag/v1.0.28
Optional layout-state screenshots remain
unverified because their separate harness host lacks System.Drawing. A proposed
CI-only assembly-load fix could not be pushed with the current credential's
workflow permissions and is not included in this release candidate. Functional
profile screenshots use their own loaded assembly and remain part of the gate.
Design review
Preserved the graphite surfaces, subdued controls and existing row hierarchy.
The search hint now names the expanded fields; hover text explains the literal,
configured-only limits. No new decoration or motion. Design reference:
Unslop by Damir Sokolovsky (@heydamir), CC BY 4.0, used as a review rubric.
Contributors
Assets 4
waX VPN v1.0.27
waX VPN v1.0.27
Copy summary in the expanded loaded-config card copies its allowlisted values
and configured-only limits to the system clipboard. It includes profile name,
addresses and DNS, but no keys or endpoints. Nothing is uploaded by the app;
clipboard sharing or sync follows the user's system settings. Copy happens
only when the button is pressed. No networking behavior or saved setting changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests passed (53 passed, one manual ignored), including clipboard
text allowlisting, key/endpoint exclusion and configured-only limits. Build and
PowerShell syntax passed. Revised preview:
https://github.com/vio137/wax-vpn/actions/runs/43177728480
Source: e8a278adb998c6d06efbbf18e262887e43359b47. All three execution jobs
passed. Actual Windows system clipboard contained the allowlisted summary and
limits without key/endpoint values. Prior summary, cache reload/restoration,
unchanged files/settings/selection/no adapter, profile/demo/recovery and installer
checks passed. Summary and installed-GUI pixels inspected.
Stable run https://github.com/vio137/wax-vpn/actions/runs/43178994579
attempt 2 passed all four jobs on source
dcde1825248f5230c6862297db9a11a9b6c4202c. Actual retry evidence checked:
tunnel-address ping, clipboard content, summary/cache reload, local-state
preservation, profile and recovery assertions, startup and installer proof.
Recovery took 4 seconds; disabled recovery remained off in 48 samples over 12
seconds; 344 console samples saw no window, with shorter flashes still possible.
Retry summary and installed-GUI pixels inspected. Optional layout-state captures
remain unverified because the separate harness host did not load System.Drawing.
Published installer downloaded and SHA-256 matched its published checksum:
5e1f7c11d164e31715df4628cb5869896bd2203f259c8d336ecc633b49d57099
(11,768,661 bytes).
https://github.com/vio137/wax-vpn/releases/tag/v1.0.27
Preview failure and correction
The first preview (43175710700, source 95e4514) failed the actual Windows
clipboard-content check: Copy summary did not update the system clipboard.
Inspection found the software backend's egui-winit OS clipboard feature was
disabled, using app-internal fallback text. Enabled its existing arboard feature
for OS text clipboard support; no third-party crate version changed. Revised
Windows actual clipboard-content check passed in the revised preview. This also enables OS clipboard integration for other
text controls on this backend. No network behavior changed.
First stable-gate attempt
Run 43178994579 attempt 1, source dcde182, stopped publication. The demo
peer handshake passed, but its tunnel-address ping to 192.168.4.1 failed.
The accumulated failure also made the later GUI step fail; its functional
connect/recovery/disable/restore/quit assertions passed. Some optional connected
frame captures failed because System.Drawing types were not loaded in that
step; those frames are unverified.
The local profile/clipboard and startup-soak steps did not run in this attempt.
Build and fresh-runner installer jobs passed. Retried the failed gate once on
the exact same source without weakening any assertions. Attempt 2 passed the
tunnel ping and full gate. The original failure remains recorded here.
waX VPN v1.0.26
waX VPN v1.0.26
The loaded-config summary reuses its allowlisted display strings while the
selection and loaded profiles are unchanged, instead of rebuilding its values
every frame. Switching profiles or successfully reloading profiles refreshes
the cache. Only display text is cached, never a config or key material.
The visible summary and networking behavior are unchanged. No measured speedup
is claimed. The cache is bounded to one selected profile.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests passed (52 passed, one manual ignored), including reuse,
selection changes and explicit invalidation after same-index replacement.
Build and PowerShell syntax passed.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43173001910
Source: 9888c33085f67f1edfd55c7a7d9feb36551bfc86. All three execution jobs
passed. Actual Windows results passed selected-config address change at the
same index, reload refresh, restored original bytes and second reload refresh,
unchanged selected settings and no adapter. Prior summary/profile/demo/recovery
and installer checks passed. Reloaded-summary and installed-GUI pixels inspected.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43174042593
Source: 4a2488390a3c7e589f2afb05218749daaeba4210. All four jobs passed.
Actual full results passed same-index reload/restoration cache refresh and prior
summary/profile checks, demo handshake/tunnel-address ping, DNS/MTU restore,
split-route checks, 4-second recovery, recovery-disable with 48 samples over
12 seconds, manual reconnect, original HWND/PID restore and graceful quit.
No console observed in 341 samples at about 100 ms; shorter flashes can be missed.
Stable reloaded-summary and installed-GUI pixels inspected. Installer passed.
Published installer (11,712,294 bytes) downloaded and independently hashed,
matching SHA256SUMS-v1.0.26.txt:
89187ae6e6e3d9c3b074f79750dea2637ebdd9ab46eccb1193af6cbedc2015cf.
An initial test fixture omitted the required Peer section; corrected before
passing the tests. No app runtime failure was found by that fixture error.
waX VPN v1.0.25
waX VPN v1.0.25
The read-only loaded-config summary now lists explicit /0 default-route
families: IPv4 only, IPv6 only, both, or none. It checks all loaded peers,
without inferring coverage from split prefixes. This describes configured
AllowedIPs, not current routes, Internet reachability or leak protection.
Keys remain excluded. No saved setting or networking behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests passed (51 passed, one manual ignored), including single,
dual-family, multiple-peer and split-prefix cases. Build and PowerShell syntax passed.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43170288176
Source: fcf9c405ee1d130819d4ed9756889f0fe98d4d62. All three execution jobs
passed. Actual Windows summary showed the explicit /0 None row, expanded and
collapsed, excluded keys and kept files/settings/selection unchanged without
creating an adapter. Prior profile/demo/recovery and installer checks passed.
Summary and installed-GUI pixels inspected.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43171320662
Source: 7a4b38f71a2feb553eef90c623e3968c4ab0395d. All four jobs passed.
Actual full results passed explicit-default summary and prior profile checks,
demo peer handshake/tunnel-address ping, DNS/MTU restore, split-route checks,
4-second recovery, recovery-disable with 48 samples over 12 seconds, manual
reconnect, original HWND/PID restore and graceful quit. No console observed in
336 samples at about 100 ms; shorter flashes can be missed. Stable summary and
installed-GUI pixels inspected. Fresh-runner installer checks passed.
Published installer (11,712,549 bytes) downloaded and independently hashed,
matching SHA256SUMS-v1.0.25.txt:
6ff166544c82dec3ed34c1008100cb2b98ba778b72847350f65ae132ff0c3918.
No performance claim.
waX VPN v1.0.24
waX VPN v1.0.24
The Connect quick picker shows a quiet match count during local searches,
including singular and zero results. Clearing the search removes the count.
The filtered list stays shorter to keep the Connect action visible. No new
saved setting, file access, network request or connection action was added.
Search still matches every word across profile names and endpoints; a number
can match an endpoint as well as a profile name.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Short local checks: app tests passed (50 passed, one manual ignored), build
and PowerShell syntax passed.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43167217900
Source: e04344c94d8c2bacc6136c16ca24568e71ad9209. All three execution jobs
passed. Actual Windows results passed singular/zero counts, Clear removing
count, unchanged selection/no adapter, and 26-profile list/Connect bounds.
Prior profile, loaded-summary, demo tunnel/recovery and installer gates passed.
Installed-GUI and one-match picker pixels inspected.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43168675659
Source: 5870fb7751e1e4536845eb5a4eb78b56a79d4ca5. All four jobs passed.
Actual results passed count/Clear/bounds and prior profile/summary checks,
demo peer handshake/tunnel-address ping, DNS/MTU restore, split-route checks,
3-second recovery, recovery-disable with 48 samples over 12 seconds, manual
reconnect, original HWND/PID restore and graceful quit. No console observed in
326 samples at about 100 ms; shorter flashes can be missed. Stable installed-GUI
and one-match picker pixels inspected. Fresh-runner installer checks passed.
Published installer (11,711,798 bytes) downloaded and independently hashed,
matching SHA256SUMS-v1.0.24.txt:
e46377fe9961f2d33eb6d5fca1a66baa5f7ec55c05ea00ea85e5ae3c7abe5904.
No performance improvement is claimed.
waX VPN v1.0.23
waX VPN v1.0.23
Dependency review and one scoped patch update: crc32fast 1.5.4 -> 1.5.5,
used by image/PNG decoding through eframe. No Windows x64 speedup is claimed.
No networking/TLS/certificate package was updated.
cargo-audit 0.23.0 scanned 571 lockfile dependencies against RustSec DB commit
fd6f39814c4d3c359fdbe223d0280dec4933f78f (2026-11-11). It reported zero
vulnerability entries but six warnings, unchanged after the update: glib0.18.5
unsoundness and five unmaintained crates. None appears in the default Windows
x64 target dependency graph; all remain in the cross-platform lockfile.
This is not a clean-security claim. See docs/dependencies/v1.0.23-review.md
and raw before/after reports for warnings, deferred updates and scan limits.
No tunnel, DNS, firewall or service behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local workspace tests passed after the patch: 104 passed, one manual test ignored.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43164420215
Source: 17920a2c1a2bb29cdcfd808795f0d7bf77485d23.
All three execution jobs passed. Actual Windows proof passed prior profile,
summary, demo connection/recovery and installer gates. Installed-GUI and summary
pixels were inspected.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43166024496
Source: 1069d029c4864fd8441a3c1432c635415bf66dcb. All four jobs passed.
Actual artifacts passed demo registration, peer handshake/tunnel-address ping,
DNS/MTU restore, split-route checks, recovery after 3 seconds, recovery-disable
with 48 samples over 12 seconds, manual reconnect, original HWND/PID restore,
and graceful quit. No console was observed in 327 samples at about 100 ms;
shorter flashes can be missed. All profile and key-free summary checks passed.
Installed-GUI and summary pixels were inspected. Fresh-runner installer passed.
Published installer (11,711,595 bytes) was downloaded and independently hashed;
it matches SHA256SUMS-v1.0.23.txt:
32ae6de02ed82d29e350f0cc7339b7337065c51728a8c6617e842611ae17f94f.
Advisory scan covers known RustSec crate-version advisories,
not custom/vendored code, driver or installer binaries, runtime configuration,
exploitability or unknown issues.
waX VPN v1.0.22
waX VPN v1.0.22
Profiles has a hidden-by-default config summary with explicit Show and Hide actions. It shows the loaded profile's
name, addresses, DNS, MTU, peer count and configured route-entry count. Keys are
not shown. The panel explicitly labels these as configured values, not a live
connection, routing or leak check. Opening and closing it does not change
selection, settings, files or the connection.
No tunnel, DNS, firewall or service behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests: 50 passed, one manual networking test ignored. Build and
PowerShell parser passed. Summary tests cover IPv4/IPv6 values, missing values,
multiple peers, route-entry counts, unchanged config and excluded key fields.
Local collapsed and expanded pixels were inspected.
The first Windows preview passed build, installer and prior checks, but the
summary disclosure Expand action did not expose expected content. Explicit
Show/Hide buttons replace that interaction.
Revised preview: https://github.com/vio137/wax-vpn/actions/runs/43161693467
Source: 9196254d9f7a9800d3c3bd218a9b0371adae666c.
All three execution jobs passed. Actual Windows proof passed explicit Show/Hide,
expected loaded values and caveat, absent key values, unchanged profile/settings
files and no adapter. Summary and installed-GUI pixels were inspected. Prior
profile and connection/installer checks passed within the limits above.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43162857609
Source: b3c9b4e4b1fb8ba1fe59426f9eb6878061d109cd.
All four stable jobs passed. Actual stable Windows proof passed summary Show/Hide,
expected values/caveat, no key values, unchanged files/settings/selection and no
adapter. Stable summary and installed-GUI pixels were inspected. Prior demo
tunnel, DNS/IPv4 MTU/split, 4s recovery, retry disable (48 samples over 12s), manual
reconnect, original HWND/PID restore and quit passed. No console windows were
observed in 335 samples at about 100ms; shorter flashes could be missed.
Installer lifecycle, native checks and PE audits passed.
Release: https://github.com/vio137/wax-vpn/releases/tag/v1.0.22
The downloaded 11,711,556-byte installer matches the published SHA256:
8d8123ad8111cc0b371b55f26966a1207fba56d17c4b5c763fab2a0eaec7d5f3.
waX VPN v1.0.21
waX VPN v1.0.21
Clear in the Connect-page quick picker returns focus to its search editor.
You can clear and immediately type another query, including spaces, without
an extra click. Selection, profile files and connection stay unchanged.
No tunnel, DNS, firewall or service behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests: 49 passed, one manual networking test ignored. Build and
PowerShell parser passed. Local pixels showed Clear followed by a typed
Office 23 name/endpoint query, with Office 24 still selected and disconnected.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43157848403
Source: f34877982f06c88f1754616ef538843425c06eb4.
All three execution jobs passed. Actual Windows proof passed Clear returning
focus, typed name/endpoint words with spaces without connecting and repeated
Clear focus. Quick-picker focus and installed-GUI pixels were inspected.
Prior local-profile and connection/installer checks passed within the
compatibility limits above.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43159028745
Source: 0cc74a402ad8b263cf34f4a2b2e4333b257f2061.
All four stable jobs passed. Actual stable Windows proof passed Clear returning
search focus, spaced typing without connection and repeated Clear focus.
Stable focus and installed-GUI pixels were inspected. Prior demo tunnel,
DNS/IPv4 MTU/split, 3s recovery, retry disable (48 samples over 12s), manual
reconnect, original HWND/PID restore and quit passed. No console windows were
observed in 321 samples at about 100ms; shorter flashes could be missed.
Installer lifecycle, native checks and PE audits passed.
Release: https://github.com/vio137/wax-vpn/releases/tag/v1.0.21
The downloaded 11,708,272-byte installer matches the published SHA256:
578565fe0d6a92550f907bf692e74343eb2ffe13a37572cf6f4d8267c631c408.
waX VPN v1.0.20
waX VPN v1.0.20
Profiles and the quick picker match all whitespace-separated search words
across the profile name and peer endpoints. For example, Office 23 127.0.0.1
can find a profile without requiring an exact phrase. Search ignores case;
whitespace-only queries restore the list. Pinned only still applies to the
Profiles list, and searches do not select, save or connect a profile.
No tunnel, DNS, firewall or service behavior changed.
Compatibility and limits
CPU software rendering through Windows GDI remains the default. GPU rendering
is opt-in. No separate VC++/.NET/WebView2 installation is required, but Windows
system libraries, administrator consent, networking and a valid profile still
are. The bundled WireGuardNT driver is signed by its vendor. The app and
installer are unsigned and Windows may show an unknown-publisher warning.
DNS uses the native Windows API when available. netsh remains only for older
Windows builds without that API; the API-absent fallback is untested. IPv6
DNS/MTU settings checks do not prove IPv6 traffic routing or leak protection.
No kill switch is provided. Traffic can use the normal connection when the
tunnel is off. Live WARP registration is not verified.
The release gate runs on a hosted Windows Server 2025 runner with installed
runtimes and a virtual display, not a clean Windows 10/11 PC. It does not prove
the reported consumer-PC crash is fixed. A peer handshake and tunnel-address
ping do not prove Internet reachability. Tray-menu clicks need real Windows
review. Runner OpenGL rendering/dismissal remain unverified. Console-window
sampling can miss a shorter flash.
Release verification
Local app tests: 49 passed, one manual networking test ignored. Build and
PowerShell parser passed. Tests cover Unicode, repeated words, whitespace,
name/endpoint and multiple peer terms, no cross-profile matches, pins and
cached repeat queries. Local pixels showed one matching Office 23 row from
name plus endpoint words in a 28-profile list.
Preview: https://github.com/vio137/wax-vpn/actions/runs/43155412781
Source: d06638d43660d2142c5ee7f2a92eb5e122303bc2.
All three execution jobs passed. Actual Windows proof passed multi-word name
plus endpoint queries in Profiles and quick picker, every-word requirement,
whitespace reset and unchanged files/settings/selection without an adapter.
Word-search and installed-GUI pixels were inspected. Prior local profile and
connection/installer checks also passed within the compatibility limits above.
Stable: https://github.com/vio137/wax-vpn/actions/runs/43156571792
Source: fea8c74b1ddb05754629e557c266b4e490662239.
All four stable jobs passed. Actual stable Windows proof passed the new name
plus endpoint/every-word/whitespace checks and unchanged files/settings/selection
without an adapter. Stable word-search and installed-GUI pixels were inspected.
Prior demo tunnel, DNS/IPv4 MTU/split, 4s recovery, retry disable (48 samples over
12s), manual reconnect, original HWND/PID restore and quit passed. No console
windows were observed in 337 samples at about 100ms; shorter flashes could be
missed. Installer lifecycle, native checks and PE audits passed.
Release: https://github.com/vio137/wax-vpn/releases/tag/v1.0.20
The downloaded 11,708,200-byte installer matches the published SHA256:
cccb2268156b23316a603fe083aa918d93c29b9146b54538e924a33ab838f2f6.