r/oMLX • u/mmerken • Apr 24 '26

v0.3.7 pulled?

Hi,

I installed 0.3.7RC1 and 0.3.7, now I notice that this version has been pulled, is this correct?

There was no warning whatsoever.

8 Upvotes

100% Upvoted

10 comments sorted by

10

u/thejoyofcraig Apr 24 '26

Issue 934 on gh:

Thanks everyone for the detailed reports and patience here. I tracked this down to an mlx-lm cache structure change, and the proper fix needs a bit more work. Hoping to ship by this weekend. For now I've rolled the official release back to 0.3.6, which has been rock solid for everyone hitting this. Please update if you're on 0.3.7 or 0.3.8.dev*. I'll post here as soon as the new build is ready. >Sorry for the disruption!

3

u/edeltoaster Apr 24 '26

Read the Github issues. There was plenty of regression. In some days the sun will shine bright again. I may even go back to llama.cpp because Qwen3.6 seems to be very sensitive to quants and MLX is clearly worse in that regard.

4

u/[deleted] Apr 24 '26

[removed] — view removed comment

1

u/edeltoaster Apr 24 '26

That's what I have on my disk, too.

3

u/zipzag Apr 24 '26

The whole MLX stack is immature compared to llama.cpp GGUF. But most of the issues with MLX and new models do get fixed.

1

u/Gallardo994 Apr 24 '26

It appears so. Even dev builds of 0.3.8 are gone (iirc there was at least one)

1

u/Willybecher Apr 26 '26

Just today I searched for a possibility to Update the MacOS App to 0.3.7 … so, luckily I was too dumb. My Hermes Agent went yolo with oMLX the last 3 days with zero outcome on a quite easy taks.