Skip to content

feat: support Mojo 1.0.0, 1.1.0, and 1.2.0 with ARM64 CI - #109

Merged
Ahajha merged 2 commits into
modular:mainfrom
dcarp:add-latest-mojo-releases
Oct 28, 2026
Merged

Ahajha merged 2 commits into
modular:mainfrom
dcarp:add-latest-mojo-releases

Conversation

@dcarp

@dcarp dcarp commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Adds support for Mojo 1.0.0, 1.1.0, and 1.2.0, making 1.2.0 the default.

  • Pins wheel URLs and SHA-256 checksums for Linux x86-64, Linux ARM64, and macOS ARM64.
  • Preserves nightly versions and custom download mirrors.
  • Adds CI coverage for all three releases, including Ubuntu ARM64, path stripping, and fixit exports.
  • Converts the release metadata helper to Python and documents version selection.

Validation: all 14 tests pass locally on Linux x86-64 for each release, with and without path stripping. Fixit exports pass, and all platform wheel checksums and layouts were verified. ARM64 and macOS runtime validation is delegated to CI.

@dcarp

dcarp commented Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

@Ahajha, could you please approve the workflow runs for this PR? CI will validate Mojo 1.0.0, 1.1.0, and 1.2.0 across Linux x86-64, Linux ARM64, and macOS ARM64. Thanks!

Comment thread mojo/extensions.bzl Resolved
Comment thread README.md Resolved
@dcarp
dcarp force-pushed the add-latest-mojo-releases branch 4 times, most recently from 8d561a0 to 5125cac Compare October 27, 2026 08:22
Pin stable wheel URLs and checksums and make Mojo 1.2.0 the default,
while preserving nightly versions and custom download mirrors.

Test stable releases on Linux x86-64, Linux ARM64, and macOS ARM64,
including path stripping and fixit exports. Convert the release metadata
helper to Python and document version selection.
@dcarp
dcarp force-pushed the add-latest-mojo-releases branch from 5125cac to ede514d Compare October 27, 2026 08:27
@dcarp

dcarp commented Oct 27, 2026

Copy link
Copy Markdown
Contributor Author

@Ahajha, thank you for the review! I removed the pinned nightly entry while preserving nightly selection without pinned checksums.

I also streamlined the README, replaced the outdated release-snippet instructions with a link to the Bazel Central Registry, and updated the example to use version placeholders.

If this gets merged, I’ll follow up with a PR to make use of the publish-to-bcr and setup-bazel GitHub Actions and add build attestations.

@Ahajha

Ahajha commented Oct 27, 2026

Copy link
Copy Markdown
Member

Thanks, things are looking good now. One more snag, you've renamed the CI jobs, so they no longer cover the required checks. I could change that (would need to get someone who has permissions to do it), or you could merge things back into the 6 original jobs and just have extra runs in it. WDYT?

Also, appreciate the help with the BCR, it's been on our list of things to do for a long time but just never got to it.

@dcarp

dcarp commented Oct 27, 2026

Copy link
Copy Markdown
Contributor Author

Thanks, things are looking good now. One more snag, you've renamed the CI jobs, so they no longer cover the required checks. I could change that (would need to get someone who has permissions to do it), or you could merge things back into the 6 original jobs and just have extra runs in it. WDYT?

Updated some jobs to cover the 6 names.
Moving forward, do you think that it is really necessary to test on last_rc and last_green too?

@Ahajha

Ahajha commented Oct 28, 2026

Copy link
Copy Markdown
Member

Good question, Keith added that when he first was setting things up, I think it was because we were using new-ish features. That would require changing the required statuses, so let's hold off on that for now. Though maybe we should consider adding 10.x testing in the near future, since the RCs are out now.

@Ahajha Ahajha left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lights are green, thanks for this!

@Ahajha
Ahajha merged commit 4391579 into modular:main Oct 28, 2026
21 checks passed
@dcarp
dcarp deleted the add-latest-mojo-releases branch October 28, 2026 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants