The release page now carries installer_alpine_<arch>_<version>.apk. It is
built without a key from Alpine's trust store, so apk needs
--allow-untrusted.
Strings that still named v2ray-core, "v2ray / xray" or a wiki: six locales
(the core is v2raya_core; the invalid-service message, the SS plugin help,
the transparent-proxy hint, the TUN example, the custom inbound tag hint),
the --v2ray-bin, --core-startup-timeout and --plugin-manager descriptions
and their copies in the OpenRC confd files (the plugin manager is called
with --stage=parse|configuration, --link and --v2raya-confdir, not with
life-cycle stages), two comments that forbade or excused the current design,
the package descriptions that listed SSR, the AUR Go minimum (go.mod says
1.26), the systemd Documentation= and the installer's shortcut that pointed
at the wiki and the docs site, and the README sentence on network requests,
which left out the weekly release check and the NTP query on VMess failure.
The macOS section told the reader to stop the brew service and run the
binary under sudo by hand to get tun. With v2rayA/homebrew-v2raya#7 the
tap's service is one file for both identities, so the section shows the
two commands and what each gives, plus how a sudo-started service is
stopped and Homebrew's ownership warning. The requirement rows say that
an unprivileged start is lite mode by itself, as #2011 made it.
The rule data v2rayA fetches on first start is v2fly's dlc.dat and geoip.dat
(service/kernel/v2ray/asset/dat); Loyalsoldier's file is downloaded only for
the GFWList mode as LoyalsoldierSite.dat. The credit line now says so.
v2raya-user.initd is a per-user variant of the system script, not an OpenRC
user service, and its author considers it superseded; the README no longer
describes it.
The README opened with dead badges and a numbered list of places a package
might be, and sent everything else to a documentation site whose domain has
expired. It now says what v2rayA is in one paragraph, lists what a working
install needs (a v2raya_core of the same version above all), and gives one
command sequence per platform, including the APT and RPM repositories that
daeuniverse/repo-for-linux hosts for v2raya. First run, the transparent proxy
modes, where the data lives and what an upgrade from BoltDB does are stated
here instead of behind a link. The Chinese and Russian files carry the same
content; the layout follows the centred header, language line and quick
navigation used in Zakkaus/doona.
The GUI has shipped a Russian locale for years; the README did not. A
translation of the English file with the same structure and links, its
terms taken from the GUI's ru.js; the language line of all three
files points at all three.
The core has no ShadowsocksR outbound and the plugin that once served
one was removed in May, so every SSR node has been dead since. Instead
of keeping a protocol that cannot connect: an ssr:// link is refused at
import with "ShadowsocksR is not supported" and the Clash converter
skips ssr entries. A node stored by an earlier release still decodes so
it keeps its place in the list and its group ordinal; it shows as
"SSR (unsupported)", cannot be configured and can be deleted. Both
READMEs list the protocols the current core actually speaks. The GUI
side of the removal is in the GUI change that follows.
The binaries workflow, the PR workflow and build.ps1 no longer pass
-tags tinytun; there is nothing behind the tag. The Windows installer
takes wintun.dll from the official 0.14.1 package, pinned by hash, one
DLL per architecture, and deletes a tinytun.exe an earlier installer left
in the application's bin directory. The README states what the built-in
TUN does and its known limitation on Windows and macOS.
The README pointed at an image host upload from April 2020 showing an
interface that no longer exists. The new pair lives in the repository, so it
cannot disappear, and the dark one is served to readers whose system asks for
a dark theme.
release_feat_v5.yml: rewrite test 3
release_feat_v5.yml: rewrite test 4
release_feat_v5.yml: rewrite test 5
release_feat_v5.yml: rewrite test 6
release_feat_v5.yml: rewrite test 7
release_feat_v5.yml: rewrite test 8
release_feat_v5.yml: rewrite test 9
release_feat_v5.yml: rewrite test 10
release_feat_v5.yml: rewrite test 11
release_feat_v5.yml: rewrite test 12
release_feat_v5.yml: rewrite test 13
release_feat_v5.yml: rewrite test 14
release_feat_v5.yml: rewrite test 15
Test 16
Update release_feat_v5.yml
release_feat_v5.yml: Rewrite test 17
release_feat_v5.yml: Rewrite test 18
release_feat_v5.yml: Rewrite test 19
release_feat_v5.yml: Rewrite test 20
release_feat_v5.yml: Rewrite test 21
release_feat_v5.yml: Rewrite test 22
release_feat_v5.yml: Rewrite test 23
release_feat_v5.yml: Rewrite test 24
release_feat_v5.yml: Rewrite test 23
release_feat_v5.yml: Rewrite test 25
release_feat_v5.yml: Rewrite test 26
release_feat_v5.yml: Rewrite test 27