chore(release): v0.4.7

CHANGELOG.md

@@ -7,7 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.4.6] - 2026-06-19
+## [0.4.7] - 2026-06-19
+
+### Changed
+
+- **Bumped to peat-mesh 0.9.0-rc.43 + peat-protocol 0.9.0-rc.26**, bringing the
+  attachment-delivery robustness work into a runnable node:
+  - **Inbound-accepted peers register into `known_peers`** (peat-mesh#261) — a
+    single dial now suffices between two directly-connected peers; a
+    one-directional `PEAT_NODE_PEERS` no longer silently drops attachments.
+  - **Provider gossip** (`peat/blob-announce/1`, peat-mesh#262) — "who holds
+    blob X" propagates across the mesh, so a node can fetch a blob from a
+    holder it discovered rather than only the original sender.
+  - **Distribution/file-transfer implementation relocated to peat-mesh**
+    (peat#992) and the **ADR-071 interest-driven convergence seam** (peat#991,
+    opt-in; default behavior unchanged). No peat-node source change — the
+    distribution API is consumed through peat-protocol's re-export.
 
 ### Added
 

Cargo.toml

@@ -4,7 +4,7 @@ resolver = "2"
 
 [package]
 name = "peat-node"
-version = "0.4.6"
+version = "0.4.7"
 edition = "2021"
 authors = ["Kit Plummer <kitplummer@defenseunicorns.com>"]
 license = "Apache-2.0"
@@ -119,14 +119,14 @@ path = "src/main.rs"
 #
 # The `kubernetes` feature gates this PR's `KubernetesDiscovery` wiring
 # (EndpointSlice watch); it's additive on top of rc.40's surface.
-peat-mesh = { version = "=0.9.0-rc.40", features = ["automerge-backend", "kubernetes"] }
+peat-mesh = { version = "=0.9.0-rc.43", features = ["automerge-backend", "kubernetes"] }
 
 # File distribution substrate (PRD-006). FileDistribution trait + IrohFileDistribution.
 # rc.17 picks up peat-mesh rc.25 (persistent multiplexed sync streams,
 # peat#935 / ADR-063). rc.16 picked up peat-mesh rc.24 (formation_handshake
 # → &dyn QuicMeshConnection, peat#932); rc.15 was the ADR-062 Phase 2
 # consumer-side IrohMeshTransport deletion + direct-iroh-dep drop (peat#926).
-peat-protocol = { version = ">=0.9.0-rc.25, <0.9.1", features = ["automerge-backend"] }
+peat-protocol = { version = ">=0.9.0-rc.26, <0.9.1", features = ["automerge-backend"] }
 
 # P2P networking — pinned to match peat-mesh's exact iroh pin
 # (peat#923 / peat#924). peat-mesh and peat-node MUST share an iroh

crates/peat-cli/Cargo.toml

@@ -32,7 +32,7 @@ tempfile = "3"
 # workspace can't end up with two peat-mesh / iroh versions in one process
 # (iroh has process-global crypto + ALPN registries that explode under
 # version skew, see peat#923/#924).
-peat-mesh = { version = "=0.9.0-rc.40", features = ["automerge-backend"] }
+peat-mesh = { version = "=0.9.0-rc.43", features = ["automerge-backend"] }
 peat-protocol = { version = ">=0.9.0-rc.24, <0.9.1", features = ["automerge-backend"] }
 # peat-schema runtime type registry. Floor bumped to rc.22 — the ADR-066
 # hierarchy rename (peat#957) renames `platoon_id`→`cohort_id` on

src/attachments/inbox.rs

@@ -159,6 +159,7 @@ mod tests {
             started_at: chrono::Utc::now(),
             status: "distributing".to_string(),
             cancelled_at: None,
+            collection: None,
             node_statuses: HashMap::new(),
         }
     }