Skip to content

deps: bump radiance to 24a73ef (brings kindling #3554 fix)#8824

Closed
myleshorton wants to merge 1 commit into
mainfrom
bump-radiance-kindling-fix
Closed

deps: bump radiance to 24a73ef (brings kindling #3554 fix)#8824
myleshorton wants to merge 1 commit into
mainfrom
bump-radiance-kindling-fix

Conversation

@myleshorton
Copy link
Copy Markdown
Contributor

What

Bumps radiance 568c5ece24a73ef85d80 (radiance#496), which transitively upgrades:

  • kindling a9712f9521f8b144afab (kindling#36) — the fix for getlantern/engineering#3554
  • lantern-box v0.0.82v0.0.84
  • lantern-water → 958775d51395

Why (the #3554 fix)

In censored networks the Outline smart dialer fails with "no fallback was specified" (no fallback: in the smart config + all DNS/TLS strategies blocked). Previously that collapsed the entire kindling client to a non-circumventing http.DefaultTransport clone — dropping domainfront + AMP + dnstt too — which broke config fetch (Freshdesk #175766, RU/Beeline tester on 9.1.11-beta).

kindling#36 makes NewKindling log-and-degrade on a deferred-transport init failure, fatal only when no transports remain. So a smart-dialer failure now keeps domainfront/AMP/dnstt racing instead of giving up circumvention entirely.

Scope note

This is the full radiance main bump (2026-05-21 → 2026-05-29), so it also rides along recent radiance work: config-fetch coalescing (#491), IPv6 ULA TUN (#493), lantern-box bump (#495), *net.TCPConn return (#496), per-tick throughput allocations (#498). Reviewers should sanity-check those land cleanly together.

Test plan

  • CI (build-android etc.) compiles against the bumped deps.
  • Smoke a connect/config-fetch on a beta build; confirm no regression from the radiance jump.
  • Closes the radiance→lantern hop for Mobile Ad comes up for every new build #3554. (For the all-fronts-blocked RU case it's defense-in-depth — kindling keeps the other transports rather than guaranteeing connectivity.)

Refs: getlantern/engineering#3554, kindling#36, radiance#496, Freshdesk #175766.

Bumps radiance 568c5ece→24a73ef (radiance#496), which transitively upgrades
kindling a9712f95→21f8b144afab (kindling#36) and lantern-box v0.0.82→v0.0.84.

The kindling bump is the fix for getlantern/engineering#3554: NewKindling now
logs-and-degrades when a deferred transport (the smart dialer via WithProxyless)
fails to initialize — fatal only when no transports remain — instead of
collapsing the entire client to a non-circumventing default transport. Previously
a smart-dialer "no fallback was specified" error took down domainfront + AMP +
dnstt too, breaking config fetch in censored networks (Freshdesk #175766, RU).

Also rides along ~a week of radiance main (config fetch coalescing #491, IPv6
ULA TUN #493, lantern-box bump #495, *net.TCPConn return #496, throughput
allocations #498).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 29, 2026 19:41
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the radiance dependency to pick up the transitive kindling fix for degraded smart-dialer initialization, preserving other circumvention transports when one deferred transport fails.

Changes:

  • Bumps github.com/getlantern/radiance to 24a73ef85d80.
  • Updates transitive dependencies: kindling, lantern-box, and lantern-water.
  • Refreshes corresponding go.sum checksums.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
go.mod Updates the direct radiance requirement and related indirect dependency versions.
go.sum Updates module checksums for the bumped dependencies.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@myleshorton
Copy link
Copy Markdown
Contributor Author

Closing in favor or #8825

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.

2 participants