Skip to content

feat: 1.0.0-rc.0 post#458

Merged
dignifiedquire merged 4 commits into
mainfrom
iroh-rc-0
May 11, 2026
Merged

feat: 1.0.0-rc.0 post#458
dignifiedquire merged 4 commits into
mainfrom
iroh-rc-0

Conversation

@rklaehn
Copy link
Copy Markdown
Contributor

@rklaehn rklaehn commented May 8, 2026

Add draft release blog post.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
iroh-computer Ready Ready Preview, Comment May 11, 2026 11:19am

Request Review

@n0bot n0bot Bot added this to iroh May 8, 2026
@github-project-automation github-project-automation Bot moved this to 🚑 Needs Triage in iroh May 8, 2026
Comment thread src/app/blog/iroh-1-0-0-rc-0/page.mdx Outdated
Comment thread src/app/blog/iroh-1-0-0-rc-0/page.mdx Outdated
We tried very hard to get a good holepunching rate and high performance. At this point we rely on feedback from the community. If you are a user of our [stable release 0.35](/blog/iroh-0-35-prepping-for-1-0) and did not follow our fast-paced development since then, now is the time to try out the release candidate and let us know if there are any issues.

## 🔮 What happens after 1.0

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.

We ought to reference the release cycle policy in the docs, which also needs merging.

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.

dropped this paragraph for now, we can add announce this in the next RC once we have shipped that doc

@github-project-automation github-project-automation Bot moved this from 🚑 Needs Triage to 🏗 In progress in iroh May 11, 2026
Comment thread src/app/blog/iroh-1-0-0-rc-0/page.mdx Outdated
Comment thread src/app/blog/iroh-1-0-0-rc-0/page.mdx Outdated

We are confident that the wire protocol is stable. We also will be able to make significant performance and holepunching rate improvements without having to change the public API. So after 1.0, development will continue at full speed.

We expect to keep the 1.0 API stable for at least a year. Subsequent releases with major API changes will attempt to preserve wire compatibility.
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.

Don't think this matches @okdistribute 's plans. But I'm fine with this statement :)

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.

I think we might want to drop this section instead for now, and announce it once we have finalised the docs PR

@dignifiedquire dignifiedquire changed the title Draft rc release blog post feat: 1.0.0-rc.0 post May 11, 2026
@dignifiedquire dignifiedquire merged commit c3ead3d into main May 11, 2026
4 checks passed
@github-project-automation github-project-automation Bot moved this from 🏗 In progress to ✅ Done in iroh May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

4 participants