Migrate to released Mojo 1.0 and cut 0.2.0 - #6
Merged
Merged
Conversation
Re-pin pixi to the max channel and mojo >=1.0,<2; CI installs mojo==1.0.0 from PyPI instead of the nightly index with --prerelease allow. The weekly drift check still runs against the latest nightly. No source changes were needed. README test counts and measured figures re-checked against a full run on Mojo 1.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Owner
Author
|
Verification notes (generated — detail for reviewers and review tooling) All of the below ran locally on Mojo 1.0.0 (
|
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.
Mojo 1.0 shipped, so this comes off nightly. pixi moves to the
maxchannel withmojo >=1.0,<2, and CI installsmojo==1.0.0from PyPI instead of the nightly index with--prerelease allow. The weekly drift check still points at the latest nightly, so the repo keeps telling us when the language moves under it.No source changes were needed — the normalizer compiles unchanged on 1.0.
The README's unit-test count was stale: 23 → 24.
Cuts 0.2.0.
Verified locally on Mojo 1.0.0: 24 tests green, NormalizationTest.txt at 20,034/20,034,
mojo formatclean, benchmark builds and runs.