🦄 The whole family is on Mantine 9.6.3 — and this time in one pass

Hey everyone 👋

Quick maintenance round: the whole Mantine Extensions family — all 26 components, both starter templates and the Hub — is now on Mantine 9.6.3. 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 part I actually want to share is a small lesson about order. The Hub depends on 23 of the 26 components, and each starter template on three of them. Last round I updated everything in parallel, which meant the sites resolved the previous component versions and had to go through a second time. This round followed the dependency graph instead: publish the components first, wait until npm really serves them, and only then update the sites. One pass each.

The tip: wait until npm serves them is not the same as wait until publish returns. After a successful publish, npm kept answering with the old version for a couple of minutes, because it stages a release before indexing it. If your release script checks the registry right away, it will tell you the publish didn't happen — and re-running the release is exactly how you end up shipping a second, empty version.

Do you maintain a group of packages that depend on each other? I'd love to hear how you sequence your releases — 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