[25.12] sing-box: bump to 1.13.18 without Naive outbound support - #30268
[25.12] sing-box: bump to 1.13.18 without Naive outbound support#30268Ser9ei wants to merge 1 commit into
Conversation
openwrt
Bot
added
not following guidelines
release/25.12
12452f1 to
05d90f8
Compare
05d90f8 to
5e776a5
Compare
openwrt-ai
left a comment
openwrt-ai
left a comment
There was a problem hiding this comment.
Reviewed 1 new commit as a backport of the master change.
The Makefile hunks themselves are a faithful cherry-pick: comparing the resulting net/sing-box/Makefile against the post-commit file on master, the only difference is the missing PKG_CPE_ID:=cpe:/a:sagernet:sing-box line, which is pre-existing divergence of openwrt-25.12 (added to master in a75fc52) and not something this PR introduced. PKG_RELEASE is correctly left at 1 for the version bump.
Commit checks
- 5e776a5 "sing-box: bump to 1.13.18 without Naive outbound support" — the
(cherry picked from commit da594ae04b39cdc9f524962a03156c27bc3e6c83)trailer references a commit that is not reachable frommaster.da594ae0is the pre-merge commit from the contributor branch; the commit actually merged intomasterise99adbc49f7a11d0377c8135fe706c7757b9e68c(same author and author-date, committed by Hannu Nyman on 2026-08-12). A backport trailer should point at the mergedmasterSHA so the commit can be located later — please re-run the cherry-pick withgit cherry-pick -x e99adbc49f7a11d0377c8135fe706c7757b9e68c, or amend the trailer to that SHA.
Generated by Claude Code
|
|
||
| PKG_NAME:=sing-box | ||
| PKG_VERSION:=1.12.17 | ||
| PKG_VERSION:=1.13.18 |
There was a problem hiding this comment.
The upstream commit bumped 1.12.22 → 1.13.18; on this branch the same change lands as 1.12.17 → 1.13.18, because the intermediate stable updates were never backported — 1.12.18, 1.12.20 and 1.12.22 are all on master only.
So this moves openwrt-25.12 straight onto a new minor series rather than staying inside the 1.12.x series the branch currently ships. Is that the intent for this stable branch, or would backporting the remaining 1.12.x point releases be preferred? The commit body was correctly adjusted to drop the "from 1.12.22" wording, so this looks deliberate — just flagging it as a maintainer call.
Generated by Claude Code
5e776a5 to
235498b
Compare
|
The CI failure appears to be unrelated to this PR. One of the CI tests fails while downloading a package index from the OpenWrt download server. |
This patch updates sing-box to 1.13.18. Upstream release information: https://github.com/SagerNet/sing-box/releases/tag/v1.13.0 https://github.com/SagerNet/sing-box/releases/tag/v1.13.18 Scope note: The upstream Naive outbound feature is intentionally not enabled in this update. Naive outbound requires additional build system integration because it depends on Chromium Network Stack (Cronet). Depending on target and build mode, it requires either the Cronet runtime library or a Chromium-based toolchain. Upstream documentation: https://sing-box.sagernet.org/configuration/outbound/naive/#structure Changes: 1. Add upstream linker flags and compatibility build tags Add linker flags required by the sing-box upstream release build: - -checklinkname=0 Documentation: https://sing-box.sagernet.org/installation/build-from-source/#linker-flags -checklinkname=0 is required by the sing-box 1.13.x build configuration due to its use of low-level go:linkname functionality and the stricter linkname validation in newer Go toolchains. Add upstream compatibility build tags required by sing-box 1.13.x: - badlinkname - tfogo_checklinkname0 These tags are part of the upstream sing-box release build configuration: https://sing-box.sagernet.org/installation/build-from-source/#build-tags 2. Add optional CCM and OCM build options Add new optional OpenWrt configuration options: - CONFIG_SINGBOX_WITH_CCM Build with Claude Code Multiplexer service support - CONFIG_SINGBOX_WITH_OCM Build with OpenAI Codex Multiplexer service support Both options are disabled by default and are only enabled when explicitly selected by the user. The corresponding upstream build tags are: - with_ccm - with_ocm Documentation: https://sing-box.sagernet.org/installation/build-from-source/#build-tags Signed-off-by: Sergei S. <it4notice@proton.me> (cherry picked from commit e99adbc)
235498b to
a188b70
Compare
2 participants
This patch updates sing-box to 1.13.18.
Upstream release information:
https://github.com/SagerNet/sing-box/releases/tag/v1.13.0 https://github.com/SagerNet/sing-box/releases/tag/v1.13.18
Scope note:
The upstream Naive outbound feature is intentionally not enabled in this update. Naive outbound requires additional build system integration because it depends on Chromium Network Stack (Cronet). Depending on target and build mode, it requires either the Cronet runtime library or a Chromium-based toolchain. Upstream documentation:
https://sing-box.sagernet.org/configuration/outbound/naive/#structure
Changes:
Add linker flags required by the sing-box upstream release build:
Documentation:
https://sing-box.sagernet.org/installation/build-from-source/#linker-flags
-checklinkname=0 is required by the sing-box 1.13.x build configuration due to its use of low-level go:linkname functionality and the stricter linkname validation in newer Go toolchains.
Add upstream compatibility build tags required by sing-box 1.13.x:
These tags are part of the upstream sing-box release build configuration: https://sing-box.sagernet.org/installation/build-from-source/#build-tags
Add new optional OpenWrt configuration options:
Both options are disabled by default and are only enabled when explicitly selected by the user.
The corresponding upstream build tags are:
Documentation: https://sing-box.sagernet.org/installation/build-from-source/#build-tags
(cherry picked from commit e99adbc)
📦 Package Details
Maintainer: @brvphoenix
🧪 Run Testing Details