Summary
- 26.2 Pre-Release 1 shipped on 26 May 2026 and marked the end of new features for that drop.
- Pre-releases break the Tuesday snapshot rhythm and arrive whenever a batch of fixes is ready.
- By the release candidate stage, the build that ships is already decided unless something critical appears.
Minecraft’s development happens in public on a rhythm most players half-know: snapshots on Tuesdays, then pre-releases, then release candidates, then the drop. Chaos Cubed is a clean example of what each stage actually means.
Snapshots: features arrive
Weekly, usually Tuesday, and the content is whatever is ready. Features appear, change shape and occasionally vanish. Nothing in a snapshot is a promise.
Pre-releases: features stop
Pre-Release 1 landed on 26 May. Mojang’s own framing was that from this point you should mostly see bug fixes – and that pre-releases break away from the Tuesday rhythm, so the next one arrives when it is ready rather than on a schedule.
That schedule break is a useful signal. When releases start appearing on a Thursday and then a Monday, the drop is close.
Release candidates: the build is chosen
26.2 Release Candidate 1 arrived on 11 June with the standard wording: if no critical issues are found, this is the version that ships. A second candidate followed the next day to fix two critical issues, which is exactly the process working as intended.
Five days later, on 16 June, Chaos Cubed shipped.
What this means if you play on snapshots
The safe window to build something you care about is after the last pre-release, and even then a copy is wise. The risky window is the early snapshots, where a feature you have built around can still be redesigned.
Our view is that the pre-release stage is the most underrated part of the cycle for ordinary players. It is the point where the drop is feature-complete and still being fixed, which makes it the best time to test your own worlds against it and report what breaks – the feedback that arrives then still changes the shipped version.
The dates, for reference
Snapshot 6 on 5 May, Snapshot 7 on 12 May, Snapshot 8 on 19 May, Pre-Release 1 on 26 May, then pre-releases through to 10 June, release candidates on 11 and 12 June, and the full release on 16 June 2026.
Why pre-releases exist at all
Snapshots are for finding out whether an idea works. Pre-releases are for finding out whether the build is safe to ship. Different question, different kind of change, different risk to your world.
The practical difference: a snapshot can delete a feature you built around. A pre-release usually will not, but it can still revert something – which it did, twice, in this cycle.
How a bug becomes a fix
Almost every line in a pre-release changelog started as a bug report with a number. The tracker is public, the triage is public, and a well-written report with a reproduction case genuinely does move faster than a vague one. We took apart how Minecraft bugs actually get fixed, including why some famous ones stay open for a decade on purpose.
Reading a pre-release changelog with that in mind changes what you see. The list is not a list of things Mojang noticed – it is mostly a list of things players filed.
Should you play on one?
On a copy of your world, yes. On the world you care about, no. Pre-releases do not guarantee forward compatibility any more than snapshots do, and a world opened in a pre-release cannot go back.
Mods are the other reason to wait. Loaders and mods target releases, not pre-releases, so a pre-release profile is a vanilla profile by default. If you are setting one up alongside your main install, the full install process covers keeping profiles separate so nothing overwrites anything.
The 26.2 pre-release run
- Pre-Release 3, 2 June 2026 – attribute swapping reverted.
- Pre-Release 5, 8 June 2026 – hardcore change, release date confirmed.
- Release, 16 June 2026 – Chaos Cubed.
Two weeks, five builds, one significant revert. That is a normal pre-release phase.
A glossary, because the terms get mixed up
- Snapshot – experimental build, features can appear and disappear.
- Pre-release – feature set fixed, fixing and polish only.
- Release candidate – the build that ships unless something serious turns up.
- Drop – the named update, e.g. Chaos Cubed.
- Version – the number, e.g. Java 26.2.
Drops and versions are not the same thing and get conflated constantly. Wilderness Bound is the drop; Java 26.3 and Bedrock 26.50 are the versions it shipped as.
How to follow a cycle without reading everything
Read Snapshot 1 for the theme. Read the feature-complete snapshot for the contents. Read the last pre-release for the date. Skip the rest unless you are testing.
That is three articles per three-month cycle, and it gets you everything that turns out to matter.
Images: Mojang Studios, via the official Minecraft channel.