8 Commits
Author SHA1 Message Date
Markson Pigeonzilla Plus b0f7f5efc3 feat: add ci name 2026-11-14 22:32:43 +08:00
Markson Hon 878ff5802e Merge pull request #2040 from Zakkaus/aur-dispatch
ci: the AUR publish is its own workflow, callable from the release and by hand
2026-09-21 22:55:35 +08:00
Zakk 051a1711ca ci: the AUR publish is its own workflow, callable from the release and by hand
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.
2026-09-22 00:50:03 +10:00
Markson Hon b1add58fdc Merge pull request #2039 from Zakkaus/aur-push
ci: stage only tracked files in the AUR checkouts
2026-09-21 22:49:05 +08:00
Zakk b8732beddb ci: stage only tracked files in the AUR checkouts
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.
2026-09-22 00:44:46 +10:00
Zakk 063354a537 ci: the docker actions on their Node 24 majors 2026-09-22 00:34:14 +10:00
Zakk 833af7dc74 refactor: use what the dependencies already provide
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.
2026-09-20 16:40:34 +10:00
Zakk 56e734929f build: one local build entry point and one release workflow body
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.
2026-09-20 09:17:11 +10:00