mantine-json-tree 3.3.0 is out, and the story behind it is better than the changelog.
Someone opened a feature request asking for in-place editing of JSON values. Before writing a line of it, I audited the component to see what an editor would have to stand on. I never got to the feature. The audit found three bugs first, and one of them was serious enough that shipping the feature on top would have been building on sand.
Both of our Mantine documentation starters are now on Next.js 16.3 the Nextra one and the Fumadocs one, shipped together today. Dependency-only patches, nothing to migrate.
Mantine 9.5.0 came out this morning. By the afternoon every Mantine Extensions component was published on it, along with both starter templates and the docs hub.
I wish I could tell you that was skill. It's mostly one boring shell script and one rule I've learned the hard way.
The script does the whole dance per repo: branch, bump within semver, format, typecheck, lint, test, build the package, regenerate the API docs, build the docs site, test again, commit, PR, merge, publish, deploy. I run it in parallel batches and read the reports. The first repo is always done by hand though a pilot because the point of a pilot is to discover the surprise on one repo instead of on all of them.
Quick maintenance drop: I've aligned the entire Mantine Extensions family all 26 components plus the Nextra, Fumadocs and base templates to Mantine 9.4.1 (the latest 9.x).
