deps: bump radiance for the iOS peer-share gate - #8988
Conversation
radiance#605 makes the backend refuse to serve as a peer on iOS, where it runs inside the network extension on a memory budget that cannot carry the peer proxy's second sing-box instance. main already has the UI half of this from #8819, which keeps the mode unreachable on iOS. This is the half that holds when the UI is not the one asking — a setting persisted before the platform was excluded, or arriving from another device, reaches applyPeerShare directly through the auto-resume path on every launch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan includes up to 10 reviews per rolling hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe PR updates the direct ChangesRadiance dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This dependency update adds the iOS peer-share backend safeguard without broader dependency churn, and no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the pinned github.com/getlantern/radiance dependency to pick up upstream changes that add a backend-side iOS peer-share gate (and clear stale persisted peer-share state), closing a gap where iOS could still enter peer-share via persisted settings on launch.
Changes:
- Bump
github.com/getlantern/radiancefromv0.0.0-20260814212003-f59e3fe0a53btov0.0.0-20260816070116-e0df3f4b8c1d. - Update
go.sumentries accordingly (no additional module churn reflected in the diff).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| go.mod | Pins radiance to the newer pseudo-version containing the iOS peer-share backend gate. |
| go.sum | Updates radiance checksums to match the new version. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
f59e3fe→e0df3f4(v0.0.0-20260816070116-e0df3f4b8c1d)Picks up radiance#605, which makes the backend refuse to serve as a peer on iOS.
Why it matters now
#8819 landed the SmC screen on main along with the UI-side gate, so an iOS user cannot select the peer-proxy mode. But until this bump, that was the only layer — main's pinned radiance had no backend gate at all.
The UI gate covers the case where the UI is the one asking. It does not cover
resumePeerShareIfEnabled, which reads the persistedpeer_share_enabledat launch and callsapplyPeerSharedirectly. A setting persisted before the platform was excluded, or arriving from another device, would take that path on every launch with nothing to stop it. This bump closes that.It also clears the stale setting on the way through, so the state self-heals on first launch rather than retrying forever.
Verification
go mod tidyin the same commit; only the radiance lines moved ingo.mod/go.sum, no transitive churngo buildwith lantern's tags → exit 0./lantern-core/...suite greenSummary by CodeRabbit