Skip to content

Bump radiance to pick up resilient front-retry#8919

Merged
myleshorton merged 1 commit into
mainfrom
fisk/bump-radiance-resilient-retry
Jul 21, 2026
Merged

Bump radiance to pick up resilient front-retry#8919
myleshorton merged 1 commit into
mainfrom
fisk/bump-radiance-resilient-retry

Conversation

@myleshorton

@myleshorton myleshorton commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Bumps radianced7290e5, carrying the domainfront resilient front-retry work into the client. domainfront (→ db7c158) and kindling (→ ef87ee2) move with it as indirect deps.

Why

This is the last hop of the chain domainfront#15kindling#43radiance#571here.

It targets the "config fetch completely fails" reports from China/Iran, where domainfront connects (and even vets) hundreds of times but the fronted request never reaches the origin — a provider (e.g. an Aliyun edge behind the GFW) that accepts the TLS handshake but then answers 403/5xx or silently drops the request.

After this bump, fronted config fetches:

  • retry on retryable error responses (default 403 or >= 500) instead of accepting the bad response, and
  • prefer a different fronting provider on retry, so a ready queue dominated by the misbehaving-but-vetting provider doesn't trap the retries.

This PR

go.mod / go.sum only — no lantern code changes (the new behavior is automatic; the only new domainfront API is opt-in). Ran go mod tidy; go build ./... passes.

Summary by CodeRabbit

  • Chores
    • Updated underlying components to newer versions.
    • Included maintenance updates for supporting components without changing user-facing functionality.

Bumps radiance to d7290e5, which carries the domainfront resilient
front-retry work (getlantern/domainfront#15 → kindling#43 → radiance#571)
into the client. domainfront (=> db7c158) and kindling (=> ef87ee2) move
with it as indirect deps.

Fronted config fetches now retry on retryable error responses (default
403 / 5xx) instead of accepting the bad response, and retries prefer a
different fronting provider — so a provider that connects and vets but
won't forward the request (e.g. an Aliyun edge behind the GFW) is escaped
rather than re-picked. This targets the "config fetch completely fails"
reports from China/Iran.

go.mod / go.sum only; ran `go mod tidy`. `go build ./...` passes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 21, 2026 17:48
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a8b23a0e-512e-4e5e-8122-16a3e8a8907e

📥 Commits

Reviewing files that changed from the base of the PR and between fa6ff58 and 0f62312.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • go.mod

📝 Walkthrough

Walkthrough

Updates github.com/getlantern/radiance and the indirect domainfront and kindling dependencies in go.mod to newer pseudo-versions.

Changes

Dependency updates

Layer / File(s) Summary
Go module version updates
go.mod
Updates the radiance, domainfront, and kindling dependency versions; keepcurrent remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main dependency bump and the key behavior it brings in.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fisk/bump-radiance-resilient-retry

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the Go module dependencies to pull in the latest github.com/getlantern/radiance revision that includes the “resilient front-retry” behavior (via updated indirect domainfront and kindling), with no direct Lantern code changes.

Changes:

  • Bump github.com/getlantern/radiance to v0.0.0-20260721174611-d7290e50e7b4.
  • Update indirect dependencies github.com/getlantern/domainfront and github.com/getlantern/kindling to the corresponding newer pseudo-versions.
  • Refresh go.sum entries to match the new module versions.

Reviewed changes

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

File Description
go.mod Updates required radiance version and aligns indirect domainfront/kindling versions.
go.sum Updates checksum entries to reflect the new dependency versions.

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

@myleshorton
myleshorton merged commit 37d092d into main Jul 21, 2026
11 checks passed
@myleshorton
myleshorton deleted the fisk/bump-radiance-resilient-retry branch July 21, 2026 19:44
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