chore: repoint URLs at git.swaits.com and bump for release

Rewrites remaining github.com / git.sr.ht references to git.swaits.com,
translating GitHub URL shapes to Gitea's (/blob/<ref>/ -> /src/branch/<ref>/,
/tree/<tag> -> /src/tag/<tag>, /actions/workflows/X -> /actions?workflow=X,
/edit/ -> /_edit/).

Left pointing at GitHub on purpose: pull-request links (PRs were not migrated)
and GitHub-only surfaces Gitea lacks (security advisories, discussions).

CHANGELOG.md

@@ -1,5 +1,62 @@
 # Changelog
 
+## [3.0.1] - 2026-05-11
+
+### Fixed
+
+- **DHT `PublishFailing` no longer wedges the swarm for minutes at a
+  time.** Pulls in `iroh-gossip-rendezvous` 0.2.1, which retries
+  failed publishes on a 15 s cadence (default) and bypasses the
+  `1/(n+1)` write-probability gate while the DHT is unhealthy. Prior
+  to this, a single failed publish parked the bridge in
+  `PublishFailing` for at least `write_period` (5 min) and on
+  average `(n + 1) × write_period` — half an hour with a populated
+  active view — before the next retry attempt. Recovery is now
+  bounded by `failure_retry_period × consecutive_failures` and
+  flips back to `Ready` the instant a write lands.
+
+## [3.0.0] - 2026-05-11
+
+### Breaking
+
+- **`iroh` bumped 0.98 → `=1.0.0-rc.0`** and **`iroh-gossip` bumped
+  0.98 → 0.99**. The bridge is now built on iroh's first 1.0 release
+  candidate. iroh-gossip 0.99 hard-pins `iroh = "=1.0.0-rc.0"`, so the
+  bridge does too until iroh ships a final 1.0 — once it does, this
+  pin will relax to plain `"1"`. Any downstream consumer that pulls
+  iroh transitively must move in lockstep.
+- **`iroh-gossip-rendezvous` bumped 0.1 → 0.2** (now consumed from
+  crates.io; the local path-dep is gone). The 0.2 release of the
+  rendezvous crate carries the same iroh 1.0-rc.0 bump and pins
+  `ed25519-dalek = "=3.0.0-pre.7"` to match iroh-base's pre-release.
+
+### Changed
+
+- `donglora-client` resolves to 1.1.1 (was 1.0.x). Adds the
+  `connect()`-time auto-clamp of `tx_power_dbm` against
+  `GET_INFO.tx_power_min/max` and pre-flight rejection of
+  out-of-range `freq_hz` / `sf` / `bw` with
+  `ClientError::ConfigNotSupported` — both surface as ordinary
+  bridge connection errors today.
+- `Cargo.lock` refreshed end-to-end: `mainline` 6.0 → 6.1.2, plus
+  the usual tokio/rustls/hyper patch sweep.
+
+### Notes
+
+- **Pre-v2 config files were silently mis-loaded.** A stale
+  `~/.config/donglora-bridge/config.toml` from v0.x / v1.x — with
+  `sync_word = 13380` (`0x3444`, the old LoRaWAN-public default),
+  `tx_power = "22"` (old string field), or `cad = true` (removed in
+  v2) — would deserialize without error: serde silently ignored the
+  unknown `tx_power` / `cad` fields and the bridge fell back to its
+  per-field defaults, producing a "requested config" that didn't
+  match what the user had ever entered. On a shared mux the TUI
+  flagged this as a `!` against the active config. Re-run
+  `donglora-bridge config` (or update the file by hand) if your
+  config still has any of `tx_power`, `cad`, or
+  `sync_word = 13380`. A future minor will tighten the loader so
+  this fails loudly instead.
+
 ## [2.0.1] - 2026-04-25
 
 ### Fixed

Cargo.toml

@@ -1,12 +1,12 @@
 [package]
 name = "donglora-bridge"
-version = "2.0.1"
+version = "3.0.2"
 edition = "2024"
 authors = ["Stephen Waits <steve@waits.net>"]
 license = "MIT"
 description = "Peer-to-peer LoRa bridge using iroh and DongLoRa"
-repository = "https://github.com/donglora/bridge"
-homepage = "https://github.com/donglora/bridge"
+repository = "https://git.swaits.com/donglora/bridge"
+homepage = "https://git.swaits.com/donglora/bridge"
 keywords = ["lora", "bridge", "gossip", "p2p", "iot"]
 categories = ["network-programming", "command-line-utilities"]
 readme = "README.md"
@@ -15,9 +15,9 @@ exclude = [".jj/", ".github/"]
 
 [dependencies]
 donglora-client = "1"
-iroh = "0.98"
-iroh-gossip = "0.98"
-iroh-gossip-rendezvous = { version = "0.1", path = "../../iroh-gossip-rendezvous" }
+iroh = "=1.0.0-rc.0"
+iroh-gossip = "0.99"
+iroh-gossip-rendezvous = "0.2.1"
 tokio = { version = "1", features = ["full"] }
 clap = { version = "4", features = ["derive"] }
 serde = { version = "1", features = ["derive"] }

README.md

@@ -1,6 +1,6 @@
 # donglora-bridge
 
-[![CI](https://github.com/donglora/bridge/actions/workflows/ci.yml/badge.svg)](https://github.com/donglora/bridge/actions/workflows/ci.yml)
+[![CI](https://git.swaits.com/donglora/bridge/actions/workflows/ci.yml/badge.svg)](https://git.swaits.com/donglora/bridge/actions?workflow=ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 ![Rust](https://img.shields.io/badge/rust-1.94.1%2B-orange)
 
@@ -25,12 +25,12 @@ through an encrypted peer-to-peer gossip swarm.
 
 ### 1. A DongLoRa radio
 
-[DongLoRa](https://github.com/donglora/firmware) is open-source firmware that
+[DongLoRa](https://git.swaits.com/donglora/firmware) is open-source firmware that
 turns a supported LoRa development board (such as a Heltec WiFi LoRa 32 or
 similar ESP32+SX1262 board) into a USB LoRa dongle. You will need to:
 
 1. **Get a board** -- any ESP32 board with an SX1262 LoRa radio that DongLoRa
-   supports. See the [DongLoRa README](https://github.com/donglora/firmware) for
+   supports. See the [DongLoRa README](https://git.swaits.com/donglora/firmware) for
    the full list.
 2. **Flash the DongLoRa firmware** onto the board. Instructions are in the
    DongLoRa repository.
@@ -68,7 +68,7 @@ mise use -g cargo:donglora-bridge
 Or build from source:
 
 ```sh
-git clone https://github.com/donglora/bridge.git
+git clone https://git.swaits.com/donglora/bridge.git
 cd donglora-bridge
 cargo build --release
 ```

dht-partition-healing.md

@@ -3,7 +3,7 @@
 The DHT partition-healing algorithm specification is now maintained as part
 of the `iroh-gossip-rendezvous` crate:
 
-**<https://github.com/swaits/iroh-gossip-rendezvous/blob/main/PROTOCOL.md>**
+**<https://git.swaits.com/swaits/iroh-gossip-rendezvous/src/branch/main/PROTOCOL.md>**
 
 The bridge pins a specific `iroh-gossip-rendezvous` version; the spec that
 matches whatever version you're running is in

src/gossip.rs

@@ -142,9 +142,7 @@ fn spawn_receiver(
         if exit_reason == "cancelled" {
             debug!("gossip receiver stopped ({exit_reason})");
         } else {
-            error!(
-                "gossip receiver STOPPED ({exit_reason}) — this bridge will no longer receive from the swarm",
-            );
+            error!("gossip receiver STOPPED ({exit_reason}) — this bridge will no longer receive from the swarm",);
         }
     });
 }

src/main.rs

@@ -90,8 +90,7 @@ async fn main() -> Result<()> {
     info!("rate limiter: {:.1} pps", rate_limiter.rate_pps());
 
     // Create gossip network + DHT rendezvous.
-    let (swarm, gossip_event_rx, gossip_frame_tx) =
-        gossip::Gossip::new(secret_key, &cfg.bridge.passphrase).await?;
+    let (swarm, gossip_event_rx, gossip_frame_tx) = gossip::Gossip::new(secret_key, &cfg.bridge.passphrase).await?;
     let swarm = Arc::new(swarm);
 
     // Start radio.