A short notice, and an apology.
If you cloned the starter container repository between the evening of August 23 and the morning of August 24, some of its examples refuse to compile under the freshly released Mica 7.2.0 — format specifiers the 7.2 checker now validates against the actual types, and casts the release made redundant. The compiler is right and the examples were stale: they predated 7.2’s stricter compile-time checks and rode the release train unswept.
The fix is one command in your clone:
git pull— or simply re-clone. Everything else is unaffected: the published compiler packages, the Docker image, the course notebooks, and the VS Code extension are all exactly as released.
How it happened is worth stating plainly, because the repository’s whole promise is that its examples always compile in the image you pull. The repository has a gate for exactly this — every push builds every example inside the published image — but in the release window that gate was checking against a moving image tag, and the mismatch it reported was mistaken for the release race itself rather than real drift behind it. Both halves are fixed: the examples are swept to 7.2, and the gate now pins the exact compiler release the tree is written against, so it can no longer be red for the wrong reason or green about the wrong compiler.
Sorry for the stumble — and if an example still refuses to compile after a
pull, that is a bug we want to hear about: info@mica-dev.com.