@vitest/mocker 5.0.1 is affected by GHSA advisories fixed in 5.0.3
(Dependabot alerts #542 and #543). Update the lockfile within the
existing ^5.0.1 range; package.json is unchanged.
With TUN on, every proxy node IP gets a host route through the physical
gateway on macOS and Windows. A node on 127.0.0.1, such as a local
forwarder, then had 127.0.0.1 routed to the Wi-Fi gateway: loopback
broke for every process, the connectivity probe of the core API failed,
the transparent proxy paused, the routes went away, the probe recovered
and the cycle repeated. Loopback nodes are reached without leaving the
host, so collectNodeIPs drops them.
Fixes#2148
nftables 1.0.2, which Ubuntu 22.04 ships, rejects the dstnat keyword on
the output hook ("invalid priority expression value in this context"),
so the DNS redirect table failed to load and the core did not start in
redirect mode. Write the same priority as -101; nftables 1.1.7 lists it
back as "dstnat - 1".
Fixes#2133
CONTRIBUTING.md says a checklist with "checked without reading" or "AI
agent without human review" checked is closed, but nothing did it: #2138
stayed open with both boxes checked until a maintainer noticed. Close
such pull requests and issues when they are opened, edited or reopened.
The workflow reads only the body, so pull_request_target runs no code
from the pull request.
The Proxies page gains a Sort selector next to Source: default order,
lowest latency first or highest latency first. Nodes that are untested,
being tested or whose test failed stay at the end in either direction,
in their original order. compareLatency no longer reports two such
nodes as unequal, which made the sort depend on the engine. The choice
is remembered like the source and the view.
Select failed, in the batch bar, replaces the selection with the listed
nodes whose last test returned TIMEOUT or another error, so they can be
reviewed and removed with the existing Delete. Nothing is deleted
automatically. On a phone with a selection it moves into the more
actions menu.
Refs #2066
In Docker, subscription and RoutingA updates through the core dialled
the default gateway instead of 127.0.0.1, a leftover from when the core
ran outside v2rayA's container. The core now runs in v2rayA's own
network namespace and, unless port sharing is on, listens on 127.0.0.1
only. With host networking the gateway is the LAN router, and on a
bridge network the request only came back to the container when port
sharing was on and the port was published, so updates in the "proxy"
and "port rules" modes failed with connection refused.
Fixes#2139
The test builds of main pass unstable-<date>.r<count>.<commit> to nfpm
as the package version. dpkg refuses it because a Debian version must
start with a digit, and pacman reports the package as corrupted because
the version contains a hyphen; the install check added in #2123 now
fails on the first push to main. Map such versions to the pre-release
0.0.0-unstable.<date>.r<count>.<commit>, which every packager accepts
and which sorts below any release. Release versions are unchanged, and
so are the file names and the version the binaries report.
The pull request build set EXTRA_LDFLAGS as a prefix of the go build
command and expanded ${EXTRA_LDFLAGS} in the same command, which the
shell does before the prefix assignment takes effect, so the flags were
always empty. The release build sets them in the job environment and
was not affected. Use the matrix value directly.
The 2.5.14 apk carried "provides = v2raya", which apk reads as a second
package conflicting with v2raya itself, so it could not be installed on
any Alpine release; nothing in the build noticed, and no package format
was ever installed by CI. Each packaging job now installs its packages
in containers of its own architecture, under QEMU where the runner
cannot run it, and runs v2raya --version: the apk on every architecture
(loong64 from Alpine's own minirootfs, which Docker's alpine image
lacks), the deb wherever Debian publishes an image, the rpm on amd64
and arm64, the Arch package on amd64. A change under install/nfpm or
install/universal now triggers the test build that packages them.
loong64 builds with cgo for mattn/go-sqlite3, and zig targeted
loongarch64-linux-gnu, so since 2.5.14 both binaries were linked
dynamically against glibc (interpreter
/lib64/ld-linux-loongarch-lp64d.so.1). The Alpine loongarch64 package
installed but neither binary could start on musl. Target musl and link
statically instead, so the binaries run on glibc and musl systems
alike. -linkmode=external makes the core, which has no cgo package of
its own, go through zig as well; with the internal linker it cannot
resolve the libc symbols of a static build.
The image downloaded the bare v2raya and v2raya_core binaries and its
own copies of the rule data, so the Alpine package itself was never
installed by anything in the release; the 2.5.14 apk shipped unable to
install. The image now installs installer_alpine_<arch>_<version>.apk
from the release, which makes a broken apk fail the image build, and
takes its geoip.dat and geosite.dat from the package like every other
Linux package. LoyalsoldierSite.dat stays a copy of geosite.dat, as the
image has always shipped it. The script now stops at the first failed
command and on an architecture with no Alpine package.
axios 0.34 tightened its header types, and the request interceptor's
copy of config.headers into a new object no longer type-checks: the
spread carries the per-method header maps, which the index signature
now rejects. axios 0.x keeps headers as a plain object, so the
interceptor now sets Authorization and X-V2raya-Request-Id on it
directly.