PSA: debug xbuildenvs published for Pyodide 314.0.x releases were re-uploaded on 26/07/2026

I noticed that the debug cross-build environments attached to the 314.0.0 through 314.0.3 releases (added via https://github.com/pyodide/pyodide/pull/6257) have been broken in use since they were first published. This is because the archives were unpacked into an xbuildenv-debug directory, while we expect one named xbuildenv in pyodide-build. This means that pyodide xbuildenv install --debug (which I added in https://github.com/pyodide/pyodide-build/pull/371) reported a success while leaving a user with an environment whose pyodide-root did not exist, and every command after that would fail to find Makefile.envs.

Note that the nightly debug builds have never been affected, as those have always shipped the directory under the right name.

I have repacked all five stable-debug assets across those four releases with the directory renamed to xbuildenv and re-uploaded them. Nothing else about them has changed, and the checksums in the published metadata have been updated to match in #6378.

If you already have a broken debug environment on disk, you may remove it with pyodide xbuildenv uninstall and install it again (or use --force).

Since the release assets changed after the fact, this might look like a supply chain problem, but it is not, which is why I decided to open this issue. Each archive was rebuilt from the original bytes, with only the name of the top-level directory changed; the contents are otherwise identical. This should not affect the vast majority of our users either, as the debug cross-build environments have never been downloaded anywhere near as often as the regular ones. However, I felt that it's best to document this for greater transparency. I apologise for any inconvenience this may have caused. Thank you!

I will leave this issue open for a week or two in case anyone runs into it.