Upgrade iroh to 1.1.0 - #93
Merged
Merged
Conversation
iroh 1.0.3 -> 1.1.0 and iroh-mdns-address-lookup 0.4.0 -> 0.5.0 (the release built against iroh 1.1). No source changes were needed: 1.1.0's one breaking item is CustomAddr serialization, which sits behind unstable-custom-transports and is unused here. The rest is internal — relay metrics, rate-limit notifications, priority messages answered during relay reconnect backoff, DNS bound on both stacks, net-report HTTP probes honoring proxies. The relay-watchdog rationale in docs/architecture.md pinned the home-relay-loss bug to "iroh (v1.0.3)". Reworded to read as an observation on 1.0.3 that 1.1.0 does not claim to fix, so the watchdog stays. Also mark Backend::Keychain expect(dead_code) off macOS/Windows. It is only constructed under those two cfgs, so on a Linux host with the GTK dev libraries present -D warnings rejected the variant and `cargo clippy --workspace` could not run there at all. CI is unaffected: Linux excludes flextunnel-desktop, and the attribute is not emitted on the platforms that do build it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GiJ6hv634BUmnEBWLk42fz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
iroh 1.0.3 -> 1.1.0 and iroh-mdns-address-lookup 0.4.0 -> 0.5.0 (the release built against iroh 1.1). No source changes were needed: 1.1.0's one breaking item is CustomAddr serialization, which sits behind unstable-custom-transports and is unused here. The rest is internal — relay metrics, rate-limit notifications, priority messages answered during relay reconnect backoff, DNS bound on both stacks, net-report HTTP probes honoring proxies.
The relay-watchdog rationale in docs/architecture.md pinned the home-relay-loss bug to "iroh (v1.0.3)". Reworded to read as an observation on 1.0.3 that 1.1.0 does not claim to fix, so the watchdog stays.
Also mark Backend::Keychain expect(dead_code) off macOS/Windows. It is only constructed under those two cfgs, so on a Linux host with the GTK dev libraries present -D warnings rejected the variant and
cargo clippy --workspacecould not run there at all. CI is unaffected: Linux excludes flextunnel-desktop, and the attribute is not emitted on the platforms that do build it.Claude-Session: https://claude.ai/code/session_01GiJ6hv634BUmnEBWLk42fz