RetroDECK Publishes 0.10.6b Cooker Snapshot on GitHub, BIOS Refactor Continues

A cooker snapshot tagged RetroDECK 0.10.6b was published on GitHub and is explicitly marked as coming from branch main, with the release notes reading "This is a cooker snapshot based on this commit, from branch main." The GitHub release entry shows the tag name RetroDECK 0.10.6b and a publication date listed as 2026-03-01, but the supplied notes do not include the commit hash referenced by "based on this commit."

The release notes double down on RetroDECK's multi-stage publication pipeline and make clear that the project does not consider GitHub cooker snapshots to be final. The notes state "RetroDECK is NOT considered "released" until it is published on Flathub." and reproduce the pipeline sequence exactly as `Cooker (GitHub)` -> `Cooker Final (GitHub)` -> `Main RC (GitHub)` -> `Main Master (GitHub)` -> `Testing (Flathub)` -> `Stable (Flathub)`. The notes also warn that "The release might need more tweaking and Flathub fixes before the publication happens," a rationale offered for why the team explicitly tells users to avoid treating the GitHub snapshot as the finished product.

The GitHub release text in the supplied material begins with the header "## No results found" and contains repeated blocks of the publication pipeline and warnings. Changelog sections are present only as headings — "### ADDED", "### CHANGED", "### FIXED", "### UPDATED" — but list no specific items in the provided text. The release includes the literal advisory "⚠️ Avoid upgrading from GitHub ⚠️" and the phrases "Read more here:" and "Check changes since latest main release," but the supplied snippet does not include links, changelog entries, attached assets, or checksums.

The story headline references an ongoing BIOS refactor, but the release notes excerpt supplied for RetroDECK 0.10.6b contains no changelog entries describing a BIOS refactor and no commit identifier to inspect for that work. The original report also contains a truncated fragment — "with a note that RetroDECK’s formal re" — that cannot be completed from the supplied material. Those gaps leave the commit-level changes, any BIOS refactor details, and whether assets were attached to this GitHub snapshot unverified.

Given the explicit warnings and the missing details, the pragmatic course is to treat RetroDECK 0.10.6b as a developer cooker snapshot rather than an end-user release until Flathub publication occurs. Verify the full GitHub release page for the missing commit hash and any attached binaries, then monitor whether the snapshot progresses through Cooker Final, Main RC, Main Master, Testing (Flathub), and finally Stable (Flathub) as listed in the release notes. The "⚠️ Avoid upgrading from GitHub ⚠️" admonition and the repeated note that "RetroDECK releases only become officially available to everyone only after it is published on Flathub" make that sequence the definitive path for the 0.10.6b release.