feat: blog post v0.35.0 & roadmap update (#326)

* feat: blog post v0.35.0 & roadmap update

* adjust examples to new `RouterBuilder::spawn` api

* update "last updated" date in the roadmap

Author: ramfox

src/app/blog/iroh-0-35-prepping-for-1-0/page.mdx

@@ -0,0 +1,103 @@
+import { BlogPostLayout } from '@/components/BlogPostLayout'
+import { MotionCanvas } from '@/components/MotionCanvas'
+
+export const post = {
+  draft: false,
+  author: 'ramfox',
+  date: '2025-05-13',
+  title: 'iroh v0.35 - Prepping for 1.0',
+  description: 'Iroh 0.35 release',
+}
+
+export const metadata = {
+    title: post.title,
+    description: post.description,
+    openGraph: {
+      title: post.title,
+      description: post.description,
+      images: [{
+        url: `/api/og?title=Blog&subtitle=${post.title}`,
+        width: 1200,
+        height: 630,
+        alt: post.title,
+        type: 'image/png',
+      }],
+      type: 'article'
+    }
+}
+
+export default (props) => <BlogPostLayout article={post} {...props} />
+
+Welcome to a new release of `iroh`, a library for building on direct connections between devices, putting more control in the hands of your users.
+
+The number0 team has been hard at work to get a 1.0 release of `iroh` out the door this year. As we’ve gotten closer to achieving our goal, we’ve also developed a clearer understanding of what that actually looks like. We’ve mentioned in previous blog posts that a wire-protocol and network-level breaking change is coming in the near future.
+
+**This release, `0.35`, will be the last release before that protocol- and network-level breaking change.**
+
+We will continue to maintain `0.35` and will release patches if any bugs are found and fixed. Our next release—unless a bug fix between now and then requires a breaking change—will be a release candidate, which we’ll refer to as `0.99`.
+
+The `0.35` release contains minor API changes and a major update to our metrics collection.
+
+## 🧚 v0.35 Changes
+
+### **Metrics**
+
+For those of you using the “metrics” feature in `iroh`: we’ve updated how metrics collection works. Previously, we had a global metrics collector, which meant we couldn’t separate metrics when multiple instances of `iroh` were running in the same process. This was most noticeable during testing, but it could also affect users running more than one endpoint in their code.
+
+Now, metrics are collected by the `iroh::Endpoint`, so each instance can track its own metrics independently.
+
+For many users, this change will go unnoticed, as it primarily involved internal refactoring.
+
+### **Router**
+
+One API change you’ll likely notice is that the `iroh::Router::spawn()` method is now synchronous and infallible. Say goodbye to that extra `.await?`.
+
+## 🔧 Release Candidate Logistics
+
+A few key changes are coming in the upcoming `0.99-rc-alpha` release:
+
+1. **Removal of x.509 TLS certificates:** These will be removed in `0.99`.
+2. **Relay connection simplification:** Previously, connecting to the relay servers via Websockets was only available when using the "wasm" feature. Now, it is available regardless of what features you have enabled. This means we currently support two methods of connecting to relays: the old relay codec and WebSockets. The old relay codec will be removed in `0.99`. You can get ahead of the game and switch to using Websockets by using the `iroh::endpoint::Builder::relay_conn_protocol` method.
+3. **Error handling overhaul:** We currently use `anyhow` for errors. In `0.99`, we’ll move to concrete error types for our APIs.
+4. **QUIC multipath and NAT traversal:** The most significant change is our adoption of the [QUIC multipath extension](https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/14/) and [QUIC NAT traversal](https://www.ietf.org/archive/id/draft-seemann-quic-nat-traversal-01.html). This is a substantial undertaking and will form the bulk of our work as we move from a release candidate to a well-tested and trusted `1.0`.
+
+## How Does This Affect the `iroh`Maintained Protocols?
+
+`iroh-gossip` and `iroh-blobs` will follow `iroh` in moving to the `0.99` release candidate pattern after `0.35`.
+
+`iroh-gossip` will largely remain unchanged, apart from any necessary bug fixes.
+
+We’ve been working on a major `iroh-blobs` API update that will make it easier to use in general, and more specifically, will dramatically simplify tracking progress updates. Although these changes are substantial, we’re confident the new API will be more intuitive and satisfying for users.
+
+`iroh-docs` is not yet ready for a `1.0`, so we’ll continue releasing minor and patch updates as needed.
+
+## Other Crates That Will No Longer Be Maintained
+
+We will no longer update `quic-rpc` and `iroh-node-utils`.
+
+None of the `0.99` crates will depend on `quic-rpc`. Instead, we’re developing `irpc`, a new crate with fewer bells and whistles than `quic-rpc` but a much simpler and more straightforward design.
+
+To ensure the success of the `1.0` release, we’ve narrowed the scope of what `iroh` is responsible for and removed any CLI components from our roadmap. As a result, we won’t be updating `iroh-node-utils` after `0.35`, since its primary purpose was to support CLI development around `iroh` and its protocols.
+
+## ⚠️ Breaking Changes
+
+- `iroh`
+    - remove
+        - `pub fn default_from_node(url: RelayUrl, stun_port: u16) -> RelayMap`
+    - change
+        - `pub fn from_url(url: RelayUrl) -> RelayMap`, use `From<RelayUrl>` instead
+        - `Router::spawn` is now a plain function instead of an `async fn`
+        - `Router::spawn` is now infallible, instead of returning `anyhow::Result<()>`
+        - All metrics structs (`iroh::metrics::{MagicsockMetrics, PortmapMetrics, NetReportMetrics}`) now implement `MetricsGroup` from the new version `0.34` of `iroh-metrics` and no longer implement traits from `[email protected]`.
+        - Metrics are no longer registered onto the static superglobal `Core`. `iroh` does not use `static_core` feature of `iroh-metrics`. Metrics are now exposed from the subsystems that track them, see e.g. `Endpoint::metrics`.
+        - Several methods now take a `Metrics` argument. You can always pass `Default::default` if you don't want to unify metrics tracking with other sections.
+        - `pkarr::SignedPacket`, as used as a parameter in `iroh::dns::node_info::NodeInfo::to_pkarr_signed_packet` and `iroh::dns::node_info::NodeInfo::from_pkarr_signed_packet` is now expecting `pkarr` at major version `3` instead of `2`
+- `iroh-relay`
+    - change
+        - Minor change in the `From` impls for `ConnSendError` due to changing the underlying library
+
+### But wait, there's more!
+
+Many bugs were squashed, and smaller features were added. For all those details, check out the full changelog: [https://github.com/n0-computer/iroh/releases/tag/v0.35.0](https://github.com/n0-computer/iroh/releases/tag/v0.35.0).
+
+If you want to know what is coming up, check out the [v0.99 milestone](https://github.com/n0-computer/iroh/milestone/34), and if you have any wishes, let us know about the [issues](https://github.com/n0-computer/iroh/issues)! If you need help using iroh or just want to chat, please join us on [discord](https://discord.com/invite/DpmJgtU7cW)! And to keep up with all things iroh, check out our [Twitter](https://x.com/iroh_n0).

src/app/docs/concepts/router/page.mdx

@@ -27,8 +27,7 @@ async fn main() -> Result<()> {
     // identified by its ALPN. Spawn the router to start listening.
     let router = Router::builder(endpoint)
         .accept(iroh_blobs::ALPN, blobs)
-        .spawn()
-        .await?;
+        .spawn();
 
     // get our own address. At this point we have a running router 
     // that's ready to accept connections.
@@ -46,4 +45,4 @@ async fn main() -> Result<()> {
 }
 ```
 
-You can add whatever protocols you need to the router, multiplexing them all over the same endpoint.
+You can add whatever protocols you need to the router, multiplexing them all over the same endpoint.

src/app/docs/examples/gossip-chat/page.mdx

@@ -118,8 +118,7 @@ async fn main() -> Result<()> {
     // protocol.
     let router = Router::builder(endpoint.clone())
         .accept(iroh_gossip::ALPN, gossip.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     // Cleanly shutdown the router.
     router.shutdown().await?;
@@ -147,8 +146,7 @@ async fn main() -> Result<()> {
 
     let router = Router::builder(endpoint.clone())
         .accept(iroh_gossip::ALPN, gossip.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     // Create a new topic.
     let id = TopicId::from_bytes(rand::random());
@@ -342,8 +340,7 @@ async fn main() -> Result<()> {
 
     let router = Router::builder(endpoint.clone())
         .accept(iroh_gossip::ALPN, gossip.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     let id = TopicId::from_bytes(rand::random());
     let node_ids = vec![];
@@ -599,8 +596,7 @@ async fn main() -> Result<()> {
 
     let router = Router::builder(endpoint.clone())
         .accept(iroh_gossip::ALPN, gossip.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     // in our main file, after we create a topic `id`:
     // print a ticket that includes our own node id and endpoint addresses

src/app/docs/protocols/writing/page.mdx

@@ -39,8 +39,7 @@ async fn start_accept_side() -> anyhow::Result<iroh::protocol::Router> {
     let endpoint = iroh::Endpoint::builder().discovery_n0().bind().await?;
 
     let router = iroh::protocol::Router::builder(endpoint)
-        .spawn()
-        .await?;
+        .spawn();
 
     Ok(router)
 }
@@ -102,8 +101,7 @@ async fn start_accept_side() -> anyhow::Result<iroh::protocol::Router> {
 
     let router = iroh::protocol::Router::builder(endpoint)
         .accept(ALPN, Echo) // This makes the router handle incoming connections with our ALPN via Echo::accept!
-        .spawn()
-        .await?;
+        .spawn();
 
     Ok(router)
 }

src/app/docs/quickstart/page.mdx

@@ -123,8 +123,7 @@ async fn main() -> anyhow::Result<()> {
     // to the blobs protocol.
     let router = Router::builder(endpoint)
         .accept(iroh_blobs::ALPN, blobs.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     // do *something*
 

src/app/docs/tour/4-protocols/page.mdx

@@ -29,8 +29,7 @@ async fn main() -> anyhow::Result<()> {
     // build the router
     let router = Router::builder(endpoint)
         .accept(iroh_blobs::ALPN, blobs.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     router.shutdown().await?;
 

src/app/docs/tour/5-routers/page.mdx

@@ -29,8 +29,7 @@ async fn main() -> anyhow::Result<()> {
     let router = Router::builder(endpoint)
         .accept(iroh_blobs::ALPN, blobs.clone())
         .accept(iroh_gossip::ALPN, gossip.clone())
-        .spawn()
-        .await?;
+        .spawn();
 
     router.shutdown().await?;
     Ok(())

src/app/roadmap/roadmap.json

@@ -1,5 +1,5 @@
 {
-  "last_updated": "2025-02-25",
+  "last_updated": "2025-05-13",
   "milestones": [
     {
       "done": true,
@@ -152,21 +152,28 @@
       "description": "expand tags API",
       "tracking_issue": null
     },
-    { "version": "v0.34.0", "done": true, "released": "2025-03-18", "doc": null },
+    { "version": "v0.34.1", "done": true, "released": "2025-03-18", "doc": "https://www.iroh.computer/blog/iroh-0-34-0-raw-public-keys" },
     {
-      "done": false,
-      "title": "blobs 1.0 API",
-      "description": "overhaul blobs API",
-      "tracking_issue": null
-    },
-    {
-      "done": false,
+      "done": true,
       "title": "relay connections over websockets",
       "description": "Connections to the relay happen over websockets",
       "tracking_issue": null,
       "doc": null
     },
-    { "version": "v0.35.0", "done": false, "released": "2025-04-07", "doc": null },
+    {
+      "done": true,
+      "title": "metrics are collected per-endpoint",
+      "description": "Previously, metrics were collected globably. Now, each `iroh` endpoint collects metrics for itself.",
+      "tracking_issue": null,
+      "doc": null
+    },
+    { "version": "v0.35.0", "done": true, "released": "2025-05-12", "doc": "https://www.iroh.computer/blog/iroh-0-35-prepping-for-1-0" },
+    {
+      "done": false,
+      "title": "blobs 1.0 API",
+      "description": "overhaul blobs API",
+      "tracking_issue": null
+    },
     {
       "done": false,
       "title": "iroh-blobs: multiprovider fan-in",
@@ -184,6 +191,27 @@
         "upstream to quinn": false
       }
     },
+    {
+      "done": false,
+      "title": "QUIC NAT traversal",
+      "description": "Using Quic to traverse NATs",
+      "doc": "https://www.ietf.org/archive/id/draft-seemann-quic-nat-traversal-01.html"
+    },
+    {
+      "done": false,
+      "title": "Formalize Error Responses",
+      "description": "transition from anyhow to thiserror in all critical code paths",
+      "tracking_issue": "https://github.com/n0-computer/iroh/issues/2741"
+    },
+    {
+      "done": false,
+      "title": "release candidate",
+      "description": "publish a release candidate, seeking feedback from the community",
+      "tracking_issue": "",
+      "doc": ""
+    },
+    { "version": "v0.99-rc", "done": false, "released": "", "link": "", "expected": "H2 2025" },
+    { "ellipsis": true },
     {
       "done": false,
       "title": "draft specification",
@@ -201,50 +229,27 @@
         "iroh relay": false
       }
     },
-    {
-      "done": false,
-      "title": "QUIC NAT traversal",
-      "description": "Using Quic to traverse NATs",
-      "doc": "https://www.ietf.org/archive/id/draft-seemann-quic-nat-traversal-01.html"
-    },
-    {
-      "done": false,
-      "title": "Finalize FFI integration",
-      "description": "protocol developers have a clear path for integrating rust protocols into other languages",
-      "tracking_issue": "",
-      "doc": ""
-    },
-    { "ellipsis": true },
-    { "version": "v0.36.0", "done": false, "released": "2025-04-21", "doc": null },
-    {
-      "done": false,
-      "title": "Formalize Error Responses",
-      "description": "transition from anyhow to thiserror in all critical code paths",
-      "tracking_issue": "https://github.com/n0-computer/iroh/issues/2741"
-    },
     {
       "done": false,
       "title": "finalize 1.0 spec",
       "description": "ratify the iroh 1.0 wire protocol",
       "tracking_issue": ""
     },
-    { "version": "v0.37.0", "done": false, "released": "2025-05-12", "doc": null },
     {
       "done": false,
-      "title": "release candidate",
-      "description": "publish a release candidate, seeking feedback from the community",
+      "title": "Finalize FFI integration",
+      "description": "protocol developers have a clear path for integrating rust protocols into other languages",
       "tracking_issue": "",
       "doc": ""
     },
-    { "version": "v0.38.0", "done": false, "released": "2025-06-02", "doc": null },
     {
       "done": false,
       "title": "documentation refinement",
       "description": "ensure documentation is accurate and robust",
       "tracking_issue": "",
       "doc": ""
     },
-    { "version": "v1.0", "done": false, "released": "", "link": "", "expected": "H2 2025" },
+    { "version": "v1.0", "done": false, "released": "", "link": "", "expected": "H3 2025" },
     { "all_done": false, "title": "Party", "description": "That's it. All done. no more work left to do, ever. :)", "link": "https://www.youtube.com/watch?v=dQw4w9WgXcQ" }
   ]
 }