Skip to content

V 2.0

Latest
Latest

Choose a tag to compare

View all tags
@hamedcode hamedcode released this 30 Aug 07:48
· 2 commits to main since this release
V2.0
c351ed8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changelog

All notable changes to this project are documented in this file.

[2.0] - 2026-08-30

Added

  • Liveness testing pipeline (liveness/ package) — every run now tests configs in two stages before publishing anything:
    1. TCP check (liveness/tcp_check.py) — 3 rounds of TCP handshake, run directly from the GitHub Actions runner. Cheap, fast, and drops configs whose port isn't even open.
    2. Real proxy test (liveness/wireguard.py, liveness/xray_knife_test.py) — configs that survive stage 1 are tested with xray-knife from behind a WireGuard tunnel, so target servers see a VPN exit IP instead of GitHub's IP range (avoids flagging/blocking servers that are sensitive to datacenter/CI IPs).
  • Multi-WireGuard failover — the WG_CONFIGS secret can hold several WireGuard configs (e.g. multiple ProtonVPN servers); if one tunnel fails to come up or drops mid-run, the pipeline automatically tries the next one.
  • sub/top100.txt — the fastest configs that passed both stages, ranked by latency.
  • sub/clash.yaml — a ready-to-import Clash/Mihomo config built from the same top set (supports vmess, vless including Reality, trojan, and shadowsocks).
  • docs/WIREGUARD_SETUP.md — step-by-step guide for exporting a WireGuard config (e.g. from ProtonVPN) and adding it as the WG_CONFIGS repo secret.
  • New "Live Configs" section in README.md showing a stage-by-stage funnel: how many configs were fetched, how many passed TCP, and how many passed the real WireGuard test — so it's clear at a glance which stage is actually working on a given run.
  • requirements.txt (added pyyaml, needed for clash.yaml generation).

Changed

  • Dead configs are no longer published. Previously, every fetched config was written to sub/ and detailed/ regardless of whether it worked; now the TCP check (stage 1) runs before any output files are written, and only configs that pass it are categorized and committed to the repo.
  • .github/workflows/main.yml now installs wireguard-tools and downloads/verifies a pinned xray-knife release (SHA-256 checked) before running the script.
  • The README summary table now includes a "Published (passed TCP check)" row alongside the existing fetched/unique/duplicate counts.
  • If the WG_CONFIGS secret is missing or every WireGuard tunnel fails to come up, the pipeline no longer fails the workflow — it falls back to TCP-only ranking for top100.txt/clash.yaml and states that explicitly in the README instead.

Fixed

  • WireGuard configs with dual-stack Address/DNS fields (comma-separated IPv4 + IPv6, as exported by ProtonVPN) were mishandled — ip address add only accepts one address at a time, so the tunnel failed to come up. Each value is now applied individually.
  • The network namespace used for the WireGuard tunnel had no DNS resolver, so every health-check (and later, hostname-based config tests) silently failed. /etc/netns/<namespace>/resolv.conf is now generated from the tunnel's own DNS entry (with a public fallback).
  • A single malformed config (a remark/name containing a NUL byte) would corrupt xray-knife's CSV output enough that Python's CSV parser rejected the entire file — discarding thousands of otherwise-valid real-test results and silently falling back to TCP-only ranking. NUL bytes are now stripped before parsing, so one bad config no longer takes the whole batch down with it.
Assets 2
Loading