[Mjboothaus]

Adds mojo-toml v0.5.1 - Native TOML 1.0 parser and writer for Mojo.

Changes from previous PR #193:

• ✅ Added package image (recipes/mojo-toml/image.png) for builds.modular.com display per reviewer request
• ✅ Enabled CodeQL scanning and added badge to repository README
• ✅ Bumped to v0.5.1 to mark this enhanced release

Package features:

• Complete TOML 1.0 specification support
• Array of tables [[section]] syntax
• Alternative number bases (hex, octal, binary)
• TOML writer with round-trip fidelity
• 168 comprehensive tests (100% passing)
• Zero Python dependencies

Repository: https://github.com/DataBooth/mojo-toml
CodeQL:

Supersedes #193

[bgreni]

Looks like there is an error in your recipe, also I believe the mojo version you would be looking for is 0.25.7 (though 0.26.1 is coming soon)

[Mjboothaus]

Hi - thanks @bgreni - as a bit of an aside see also #195 - I think this might be a modular-community repo issue that causes some errors too?

Actually I think the macOS build failure was specifically because the CI couldn't find tag v0.5.0 when the package version declared 0.5.1 - this is now resolved.

Looking more closely - the main issue is that the recipe schema expects:
• tests (plural) instead of test
• documentation instead of doc_url
• repository instead of dev_url

Ok so version should be pinned to latest stable (25.7)? I am now doing the following with the version:

context:
  version: X.Y.Z
  mojo_version: "=0.25.7"

package:
  name: mojo-*
  version: ${{ version }}

requirements:
  build:
    - mojo-compiler ${{ mojo_version }}
  host:
    - mojo-compiler ${{ mojo_version }}
  run:
    - ${{ pin_compatible('mojo-compiler') }}

which is apparently what other packages do.

---

Furthermore made the following enhancements to improve my build reliability:

Fixed recipe schema compliance issues and standardised Mojo version management across all of my 5 mojo packages including mojo-toml (especially adding local validation):

• ✅ Schema fixes: Changed test: → tests:, doc_url → documentation, dev_url → repository per rattler-build requirements
• ✅ Version standardisation: All packages now use mojo_version: "=0.25.7" in context with pin_compatible() for runtime
• ✅ Pre-commit enforcement: Installed hooks in all repos, fixed trailing whitespace in 30+ files
• ✅ Local validation: Added rattler-build validation scripts to catch schema errors before submission

[Mjboothaus]

Actually, still doing some further work to make it more bulletproof - will comment when ready for review

[Mjboothaus]

@bgreni - While running pixi run build-alllocally I noticed pixi warns that the top-level project field is deprecated in favour of workspace. Not changed in this PR since it’s orthogonal to mojo-toml, but happy to open a follow-up PR to update the manifest if that’s helpful.

[Ahajha]

@Mjboothaus BTW I did some spring cleaning, rebasing should fix the CI being stuck as well as the Pixi warning. Also CI will be using the latest Pixi now.

[bgreni]

@Mjboothaus Looks like everything is fixed up now, thank you for your patience, ironically 26.1 was released this week so did you want to do one last upgrade before we start merging these in?

[Mjboothaus]

@Mjboothaus Looks like everything is fixed up now, thank you for your patience, ironically 26.1 was released this week so did you want to do one last upgrade before we start merging these in?

Yes would seem to make sense for all of my packages to test against 26.1 - thanks also @Ahajha - I have continued to do some housework locally to make things more robust - so will try and work out how to submit all this.

[Mjboothaus]

Update:

• migrated mojo-toml recipe to Mojo 0.26.1.
• context.mojo_version is now '=0.26.1' in recipes/mojo-toml/recipe.yaml.
• The mojo-toml library has been migrated and tested on Mojo 0.26.1 (tests and benchmarks) in the mojo-toml repo.
• Local 'pixi run build-all' on this branch shows mojo-toml building successfully; remaining errors are from other recipes / MAX channel availability, not this one.

[Mjboothaus]

@Mjboothaus BTW I did some spring cleaning, rebasing should fix the CI being stuck as well as the Pixi warning. Also CI will be using the latest Pixi now.

@Ahajha Pixi action seems to be using pixi v0.37 ?

[Ahajha]

Where are you seeing that? The action itself might need to be updated, but the Pixi version itself should be 0.63.2, see: https://github.com/modular/modular-community/actions/runs/21573472685/job/62159294743#step:3:3

[Mjboothaus]

Yes I saw it in the GH actionSent from my iPhoneOn 2 Feb 2026, at 4:13 pm, Alex Trotta ***@***.***> wrote:Ahajha left a comment (modular/modular-community#196) Where are you seeing that? The action itself might need to be updated, but the Pixi version itself should be 0.63.2, see: https://github.com/modular/modular-community/actions/runs/21573472685/job/62159294743#step:3:3 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[Mjboothaus]

I noticed it in mojo-yaml - in the GH prefix-dev/setup-pixi@v0.9.3 action -- presumably it is common to all?

[Ahajha]

@Mjboothaus https://github.com/DataBooth/mojo-yaml/actions/runs/21574660967/job/62159669994 That's your repo, totally out of our control :) You'll want to make a similar change on your side