Sanaei 29557e2153 fix(sub): gate the VLESS flow in JSON subscriptions like raw and Clash links ... genVless emitted client.Flow unconditionally, while the raw link (service.go:806) and the Clash proxy (clash_service.go:251) both gate it behind vlessFlowAllowed. A flow_override left on client_inbounds after its inbound moved to a transport Vision cannot use -- ws, grpc, httpupgrade -- therefore survived only into the JSON subscription, handing that client an outbound xray-core rejects while its other two formats were correct. Apply the same gate at the call site, reading the network from the per-host stream so a host that rewrites the transport is judged on what it actually emits. Verified by seeding a flow_override on a ws+tls inbound: before, raw and Clash dropped the flow and JSON kept it.		2026-07-25 00:51:48 +02:00
..
config	v3.5.0	2026-07-12 22:08:19 +02:00
database	fix(hosts): assign group ids to imported hosts and repair empty ones	2026-07-23 18:52:42 +02:00
eventbus	Repo-wide self-correcting audit: 54 verified bug fixes (#5970)	2026-07-17 00:33:06 +02:00
logger	fix(inbounds): apply runtime changes after the DB commit (#5768)	2026-07-08 22:12:28 +02:00
mtproto
sub	fix(sub): gate the VLESS flow in JSON subscriptions like raw and Clash links	2026-07-25 00:51:48 +02:00
tunnelmonitor
util	Repo-wide self-correcting audit: 54 verified bug fixes (#5970)	2026-07-17 00:33:06 +02:00
web	perf(clients): take one email snapshot per client fan-out, not one per inbound (#6091)	2026-07-25 00:51:48 +02:00
xray	Bug-label issue sweep: 16 fixes (#6083)	2026-07-23 15:34:42 +02:00