In other words, it hasn't shipped.

The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development, at least for large porting projects like this one, and for many people on this site that is a high stakes question.

To prove that, a proper release is needed, and the Bun community needs to adopt it. There's a huge partisan eagerness to declare the Claude Code release or anecdotal experiences on the canary as victory, but the viability of 1.4 hasn't been demonstrated until it has been released and adopted by the bulk of the community.

There isn't actually any hurry on that. Nobody needs Bun 1.4 tomorrow. It's Jarred that keeps saying it'll be released tomorrow, while the code churns at an astonishing rate (see below). People with a skeptical outlook will inevitably suspect that he doesn't have confidence in the release and is struggling to acquire it.

Github insights for the last week:

> Excluding merges, 57 authors have pushed 349 commits to main and 6892 commits to all branches.

> On main, 2026 files have changed and there have been 189,502 additions and 133,836 deletions

> The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development

To who? You?

> To prove that, a proper release is needed

For who? Who is trying to prove what?

> It's Jarred that keeps saying it'll be released tomorrow

There's no official blog... he's just rambling on x?

> Github insights for the last week

That's the problem with the rest of your post. Bun is no longer VC-fueled open source project. It got sold to Anthropic.

> There's a huge partisan eagerness to declare the Claude Code release

Hence there isn't. The Claude Code release is for its own use.