The Release_to_AUR job of _release.yml moves to _release_aur.yml (workflow_call,
input tag); the release calls it as before, after GitHub_Release and only with
publish_downstream. release_aur.yml runs it alone from workflow_dispatch, for the
case where the release went through and only the AUR step failed, as with 2.5.5.
833af7dc replaced 'git add .SRCINFO .INSTALL && git commit -a' with 'git add -A',
which also staged the installer_archlinux_*.pkg.tar.zst that updpkgsums downloads
into aur/v2raya-bin; the AUR hook rejected the 2.5.5 push (maximum blob size
488.28KiB exceeded). 'git add -u' stages the PKGBUILD and .SRCINFO changes and
the .INSTALL deletion, and nothing new.
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.
copyfile, the empty ports/ss.go stub, parseDnsAddr and DnsRouting (the DNS
config is generated for the core's module now), the Inter font and the
switch-menu icon of the old GUI, the docs-site dispatch workflow (the site is
retired; the docs are in the app), the unused v2ray_arch in the docker helper,
the root .gitignore rule for a web directory that moved, and the .dockerignore
patterns for binary and test names that no longer exist. The skipped
TestFillEmpty asserts what FillEmpty does instead of what it once did.
A daily job lists open issues not updated for 60 days, except those labeled
notice or enhancement, and closes up to 100 of them as not planned with a
comment; there are 220 such issues today, the oldest from 2024.
A read of the tree for home-grown code that a dependency or the platform
covers. Each item names what replaces it.
- IPv4 CIDR membership was a binary-string trie (infra/dataStructure/trie)
fed with CIDRs rendered as bit strings; net.IPNet.Contains, which the
same file already used for IPv6, does it. The trie package is gone.
- The response replay cache was an LRU with its own linked list, indexes
and timeout strategy (infra/dataStructure/lru), of which one fixed-size
instance existed; hashicorp/golang-lru/v2, already in go.mod, is that
cache, typed. go mod tidy also dropped go-nanoid, which nothing imported.
- The HTTP client for subscription updates through the local proxy carried
a CONNECT dialer of its own (pkg/util/proxyWithHttp); http.Transport's
Proxy handles socks5:// and http:// URLs, resolves hostnames on the
SOCKS proxy and uses CONNECT for https. Verified on the VM: a
subscription update succeeds in both "pac" and "proxy" modes.
- core/dns/qtype.go listed nine type names in two switches before falling
back to miekg/dns tables that contain the same names; dns.Type.String
and dns.StringToType are the tables.
- The GUI tracked prefers-color-scheme with its own media query and
toggled a theme-dark class nothing reads any more; Vuetify's "system"
theme follows the OS itself. Verified in headless Chrome: auto follows
the OS in both directions, an explicit choice overrides it.
- The AUR packages carried .INSTALL hooks whose only content was a
coloured "Completed!" banner, duplicated in the deb/rpm after-install
scripts; pacman and apt report that themselves. The hooks are gone, the
release workflow stops copying them, and after_install/after_upgrade
keep only daemon-reload and the restart.
- The tap release job downloaded eight artifacts in eight steps;
actions/download-artifact takes a pattern with merge-multiple.
Three service packages outside the executable's dependency graph
(common/antiPollution, pkg/util/gopeed, kernel/vmessInfo), a blank
import of miekg/dns the core already imports, the --core-type flag no
code read, the PutAccount handler whose route was commented out, two GUI
API wrappers without a caller, two .SRCINFO files the release regenerates
and an unreferenced runit sample. The workflow path filters watched a
root go.mod that does not exist and the PR build skipped core/.
build.sh and build.ps1 each built the GUI, the core and the service
their own way, and nothing in the repository ran them; build.sh passed a
with_gvisor tag no source file declares. build.sh now runs the same
commands as _build_web.yml and _build_binaries.yml, takes the version as
an argument or from git describe, and stops at the first failing step;
build.ps1 is the same sequence for PowerShell.
release_main.yml and beta_release_main.yml duplicated every release job
and had drifted (the beta looked the release up in a hard-coded
repository). Both now call _release.yml with the tag, a prerelease flag
and whether to publish to the downstream package channels.
The toolchain of the rewrite: Vite with vite-plugin-pwa (autoUpdate,
/api/ never cached), vue-tsc, ESLint's flat config, Vitest with
happy-dom and a mount helper, an i18n check and a gzip size gate in CI,
Red Hat Text self-hosted under /static/fonts.
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 vendored core/xray submodule is dropped. xray-core is now pinned via a
go mod pseudo-version resolving to v26.7.28 (commit 5ca6f4b7); v26 tags are
not directly resolvable because Xray's module path lacks the /v26 suffix, so
the pin must be made by commit hash. CI workflows and the AUR PKGBUILD no
longer need "submodules: recursive" / "git submodule update".
The juicity and tuic outbounds are ported from softwind to
github.com/daeuniverse/outbound (temporarily replaced with an olicesx fork
pending sticky-ip support):
- Dialer calls use DialContext; the network string is decoded with
netproxy.ParseMagicNetwork instead of a "udp" prefix check, since it may
be binary-encoded via netproxy.MagicNetwork.
- A packetConnAdapter wraps xray's UDP dial result: outbound asserts the
underlay conn to netproxy.PacketConn whose ReadFrom/WriteTo signatures
(netip.AddrPort / string) differ from net.PacketConn, while xray returns
*internet.PacketConnWrapper.
The <<< here-string appends an extra newline to the key file, which can
corrupt OpenSSH private key format and cause 'Bad passphrase' errors.
printf writes the exact content of the variable without modification.
- Add v2raya_core source downloads and checksums for all architectures
in PKGBUILD and .SRCINFO
- Install v2raya_core to /usr/bin/v2raya_core in package step
- Update deploy_v2raya_bin.sh to compute and substitute v2raya_core hashes
- Fix release workflow: download v2raya_core binaries for hash computation
- Fix release workflow: use heredoc for SSH key to avoid corruption
- Fix release workflow: correct ssh-add_expect script path
- Update core/xray submodule from v1.260327.0 (v26.3.27) to v26.6.1
- Remove deprecated AllowInsecure field from all protocol structs
- Add PinnedPeerCertSha256 and VerifyPeerCertByName fields (service layer)
- Update ngui (Nuxt) frontend with text inputs for new fields
- Update gui (Vue 2) frontend with text inputs for new fields
- Keep existing PinnedSHA256 for juicity (no duplicate)
- Backward compatible: old allowInsecure params silently ignored
- Run go mod tidy to update dependencies
Download Linux arm64 service/core artifacts in release_main workflow, package them into v2raya-arm64-linux.zip, generate checksums, and upload to homebrew release assets.
- extend mips driver build tags to cover mips/mips64 variants
- update sqlite validation message to mips-family scope
- enable CGO only for Linux mips-family targets in binaries workflow
- install required mips cross compilers in CI
ci: upgrade download-artifact@v4 to v7
ci: use matrix workflow to build
ci: use matrix workflow to build
ci: use matrix workflow to build
ci: use matrix workflow to build
Squashed from:
- 916e2f66 Optimize CI: add tinytun build tag for win/mac/linux x64+arm64, abstract web build into reusable workflow
- 471b623f Remove with_gvisor build tag from all scripts and CI workflows
- bb6e2fd6 Split binary build, Linux packages, and Windows installer into reusable workflows
- 19584dcb ci: fix windows inno installer build
- 378934b8 ci: return go 1.24
Co-authored-by: Markson Pigeonzilla <marksonpigeonzilla@bugdows.cn>
Co-authored-by: Markson Hon <marksonhon@nixos.local>
Squashed from:
- 856a3730 ci: update go to 1.26
- 191be38f tun: fix IPv6 address under win
- 3ca4d5cd windows: v2rayA should read win env like %temp%
- 48a84438 windows: v2rayA should start after modified PATH
- c87bbf62 fix .exe ext-name under windows
- 614bfe1c dns: fix a error about dns format
- 991319ff pre.go: don't create C:\etc
- 9f31b39c translated all comments to English
- aaa269f7 try to fix Tun DNS
- 25c84ad9 面向云代理会话的 VS Code 中的检查点
Co-authored-by: Markson Hon <markson@nixos.local>