Skip to content

chore: sync upstream v1.14.0-beta.3 - #10

Draft
github-actions[bot] wants to merge 236 commits into
dev-nextfrom
automation/upstream-v1.14.0-beta.3
Draft

chore: sync upstream v1.14.0-beta.3#10
github-actions[bot] wants to merge 236 commits into
dev-nextfrom
automation/upstream-v1.14.0-beta.3

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Upstream release

  • Repository: SagerNet/sing-box
  • Tag: v1.14.0-beta.3
  • Commit: 1569c52957beaea308497860380d99b841c282b8
  • Copilot adaptation used: true

Validation

  • XHTTP transport tests
  • XHTTP race tests
  • HTTP/3 build-tag tests
  • uTLS build-tag tests
  • Full command-line binary build

This pull request was generated by the scheduled upstream release
synchronization workflow and intentionally remains a draft for
maintainer review.

nekohasekai and others added 30 commits July 29, 2026 19:17
Since b0c6762, every rule inside a referenced rule-set was evaluated
as if merged into the outer rule, which required tracking per-branch
group states and let outer rules and rule-set rules satisfy each
other's grouped conditions in both directions.

Restrict merging to the only designed case: a rule-set containing
exactly one non-inverted default rule is merged into the outer rule as
before. Any other rule-set now matches as an ordinary condition of the
outer rule: it matches when any of its rules matches on its own, and
its rules no longer exchange grouped match state with the outer rule
in either direction. Multiple referenced rule-sets keep OR semantics.

Flat address rule-sets such as generated geosite/geoip sets contain a
single default rule, so their behavior is unchanged. The group-state
set machinery is replaced by a single required/satisfied mask pair.

Also update the route and DNS rule docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants