- [Patch Changes](#patch-changes)#7213 056ffc2 Thanks @wicksipedia! - Publish internal package references as ranges instead of exact versions.
Internal dependencies were declared as workspace:*, which pnpm expands to an exact version when publishing ("tinacms": "3.10.0"), not a range. An exact pin cannot deduplicate against the version a consumer has already installed, so npm nests a second — and third — complete copy of tinacms and its dependency tree. In a stock Astro + TinaCMS blog this produced three copies of tinacms, three of mermaid (186 MB), five of date-fns (151 MB), and four of typescript (88 MB): about 320 MB of duplication.
The same expansion applied to peerDependencies, so packages such as next-tinacms-cloudinary and tinacms-authjs published "tinacms": "3.10.0" as a peer — requiring consumers to have that exact version or hit an ERESOLVE conflict, and forcing a republish of every dependent on each tinacms release.
Switching these to workspace:^ publishes them as caret ranges (^3.10.0), which deduplicate normally and let onlyUpdatePeerDependentsWhenOutOfRange do its job.
Updated dependencies [711ba30, 908fe7d, 566af78, b8df6ee, 59efccc, 056ffc2]:
Last Edited: July 16, 2026