This document is meant to explain the release process of Biome, and hopefully answer some questions.
The team doesn't provide ETAs (Estimated Time of Arrival). The team believes that enforcing deadlines for a group of volunteers is counterproductive, and can have negative effects on people.
We publish pre-releases of the main @biomejs/biome package twice a week. These releases are built from main, they are meant for testing and verifying that bugs are fixed.
These releases are published to pkg.pr.new, and an automated message is sent on Discord, in the #release channel.
Warning
Don't use prerelease in production. Artifacts in pkg.pr.new are purged after roughly 30 days.
Beta releases are published manually by the Core Contributors team, only this team has the right to publish these releases.
These releases can be released on request, usually right before a stable release.
Beta releases are published on GitHub, and npmjs.org under the beta tag.
Stable releases are published manually by the Core Contributors team, only this team has the right to publish these releases.
Stable releases are published on GitHub, and npmjs.org under the latest tag.
The Biome internal crates are published on crates.io on demand to avoid too much work on our end.
You can reach us out on discord if you require a version of the crates to be published.
As for now, no changelogs or tags are published when new crates are released.
All Biome crates are published under a single version.