🦄 Mantine 9.7.1 everywhere — and why two repos refused to ship

Hey everyone 👋

Another maintenance round: the whole Mantine Extensions family — all 26 components, both starter templates and the Hub — is now on Mantine 9.7.1. Peer ranges are unchanged (>=9.0.0), so there is nothing to migrate on your side, and every docs site has been rebuilt against the new version. The five components that compare themselves with a Mantine core counterpart had their comparison tables checked against 9.7.1 too: they still hold.

The part worth sharing is the two repos that refused to ship. Their update stopped at the test step, because the documentation's type check didn't recognise props that the components definitely have. The reason: that check reads the package's compiled types, and in those two checkouts the compiled folder was older than their latest feature release. The tests were comparing the docs against an API that no longer existed.

Nothing went out — the gate did its job — and a rebuild fixed both. The update script now builds before it tests.

The tip: build output is ignored by git, so nothing ever tells you it is stale. If a check reads it, produce it first, in the same run.

Have you been bitten by a stale build folder? I'd love to hear where it hid — and which component you'd like to see get some love next.

📚 Hub: https://mantine-extensions.vercel.app/

📦 npm: https://www.npmjs.com/org/gfazioli

💻 GitHub: https://github.com/gfazioli