Release 0.10.0: promote the release candidate unchanged - #115
Merged
Conversation
0.10.0rc1 did its job. It published through trusted publishing, installed from the real index on machines that never built it, and served a WSGI app. Nothing needed fixing afterwards, so this is the same artifact under a stable number -- version strings only, no source changes. The changelog keeps what the rc cost, because the reasoning outlives the incident: three attempts, four defects, every one invisible from the machine that built the artifact. The sharpest was SIGILL from `mojo build` defaulting --target-cpu to the build host, which no static check could have found -- the binary was correct, it just needed instructions the consumer's CPU did not implement. Verified at 0.10.0: builds, `m0serve --version` reports it, smoke-wheel and smoke-serve green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version strings and changelog. No source changes from
0.10.0rc1.The rc did what it was for: published through trusted publishing, installed from the real index on machines that never built it, and served. Nothing needed fixing afterwards, so this is the same artifact under a stable number.
What the rc cost, and why the changelog keeps it
Three attempts, four defects, every one invisible from the machine that built the artifact:
mojo builddefaults--target-cputo the build hostwheel-consume-linuxotoolis macOS-only, so Linux couldn't inspect half the wheelswheel-inspectpublishsucceedThe first is the one that would have shipped. It isn't detectable by static inspection at all — the binary is correct, it just needs instructions the consumer's CPU doesn't implement. Only running it on different silicon finds it, which is exactly what those jobs do.
After merge
Tag
v0.10.0.publish-pypiuploads on the same proven path; the pre-release flag now infers correctly from the tag, sov0.10.0will publish as Latest and0.10.0rc1stays marked Pre-release.Test
m0serve --versionreports0.10.0;smoke-wheelandsmoke-servegreen;check-docsagrees across all three version copies (pyproject.toml,M0SERVE_VERSION,uv.lock).🤖 Generated with Claude Code