Changelog - 2026-10-18
A package depends on its siblings at the exact version released with it
Bug FixIn one line. @venizia/ardor X now needs @venizia/ardor-kernel, -react and -admin at exactly X, not at ^X.
What changed
- The cause. The siblings were caret ranges. A caret on a prerelease accepts a later prerelease of the same patch, so a fresh install of
@venizia/ardor@0.1.4-3pulled 0.1.4-4 of the other packages, whereDefaultAuthProvider.loginhas another type, and failed withTS2416. - The fix. Each published package names its ARDOR siblings at the version released with it.
- What did not change. Dependencies outside ARDOR (IGNIS, ra-core, React) keep their caret and peer ranges.
Who is affected
Anyone who installed
@venizia/ardor0.1.4-3 or 0.1.4-4 fromnext. Pin the siblings to the same version as the umbrella, or move to the next release, where the umbrella pins them for you:bashbun add @venizia/ardor@0.1.4-3 @venizia/ardor-kernel@0.1.4-3 @venizia/ardor-react@0.1.4-3 @venizia/ardor-admin@0.1.4-3Everyone else. No action needed.