Skip to content

v1.2.25

Choose a tag to compare

@github-actions github-actions released this 05 Nov 21:40
· 1 commit to main since this release

CottenRouter v1.2.25

This release integrates the current Feed and SlipGate installers and their new
DNS features while retaining the Panel, connection cleanup and relay continuity
fixes from v1.2.24.

  • Feed automatically routes its main, alias, messenger and MTProto domains,
    including future native THEFEED_*_DOMAINS lists. Final native wizard choices
    are preserved on install/update, including removed aliases and disabled
    messenger domains. Native quotas, keys, media and relay settings remain intact.
  • SlipGate imports Soar alongside DNSTT, Slipstream, VayDNS and external DNS
    tunnels. Public DNS over TCP bridges to the native UDP backend, preserving
    verification probes, signed replies, pipelining and per-backend capacity limits.
  • SlipGate public-address and unrelated native settings no longer block TLS
    integration. Enabled WARP services are retained, Soar public keys are available
    through cottenrouter keys, and reintegration removes deleted/disabled routes.
  • Environment-file validation uses the final assignment, matching systemd and
    preventing a later public listener from hiding behind an earlier loopback value.

Native paths remain /opt/thefeed/data/thefeed.env,
/usr/local/bin/slipgate and /etc/slipgate/config.json.

Validation includes Go tests, the Linux race suite, vet, builds, installer staging
checks and isolated native tests against the published Feed v0.42.0 and SlipGate
v1.6.8 binaries. Feed's native wizard and generated service command retain all
four domain types, MTProto/media limits and signing identity. Real SlipGate
generates native Soar config/keys/units and returns byte-exact
signed TXT/AAAA replies through Router over UDP and TCP. These namespace checks
shim package/download/systemd boundaries; external Telegram login, outbound
MTProto/media traffic and real systemd activation remain separate checks.

Upgrade Router with its normal stable installer, then update installed backends
independently when required:

sudo cottenrouter update --project thefeed
sudo cottenrouter update --project slipgate

Both backends retain their native interactive setup and require distinct delegated
zones for the selected DNS features. Router upgrades alone do not upgrade backend
binaries.

Full Changelog: v1.2.24...v1.2.25