Bevy releases v0.18.1 to stabilize 0.18, fix regressions
Bevy's v0.18.1 patch fixes small regressions from the 0.18 milestone and is available via the release tag and short notes on Bevy's GitHub.

Bevy shipped v0.18.1 on March 2, 2026 as a follow-up patch to the major 0.18 milestone, aiming to stabilize a set of small regressions that surfaced after the larger release. The maintainers published a release tag and short release notes on Bevy's GitHub repository to mark the fix-focused update.
The patch is explicitly framed as a targeted stabilization for the 0.18 series: maintainers described v0.18.1 as intended to "stabilize small regressions" and to deliver a "handful of targeted fixes" following the 0.18 milestone. That language signals this is not a feature release but a corrective update meant to address regressions users started seeing once 0.18 rolled out.

Developers running projects on Bevy 0.18 should see concrete behavior changes from this patch. The release tag and its brief notes, posted on the project's GitHub, identify the specific commits and fixes included in v0.18.1 and provide the authoritative list for teams reproducing or verifying the regressions. Anyone tracking regressions introduced by 0.18 can use the tag to compare code and confirm whether the fixes resolve their issues.
For maintainers and integrators, the practical step is straightforward: align project Cargo.toml dependencies with bevy = "0.18.1" and test the updated tree. Because v0.18.1 is scoped to stabilization, CI runs and integration tests that failed after upgrading to 0.18 are the most likely places to validate the patch. Teams that pinned dependencies to 0.18 can adopt 0.18.1 to pick up the targeted corrections without taking on new features.
The March 2 release follows a major milestone release cadence and reflects a common post-launch cycle: ship a broad 0.18 baseline, then follow up with narrow fixes when regressions are reported. The short release notes on Bevy's GitHub provide the immediate roadmap for which regressions were addressed; developers who need exact commit references or want to reproduce fixes locally should consult the tagged release for the commit list and changelog entries.
v0.18.1 closes the immediate stabilization loop for the 0.18 series; teams depending on Bevy for engines, prototypes, or games now have a focused corrective update to incorporate and validate in their test suites.
Know something we missed? Have a correction or additional information?
Submit a Tip

