Why are 4.0.0 betas using latest dist-tag?

[idleberg]

I have noticed that the new beta versions are tagged as the latest versions – was this a conscious decision? While there are no breaking changes listed in the CHANGELOG, installing to an unstable version by default feels wrong to me.

[pi0]

c12 v4

• Migration notes: https://github.com/unjs/c12/releases/tag/v4.0.0-beta.2
• No more API changes expected, still could happen during the beta period
• Tagging release as the latest in npm was intentional for new projects to opt in (maintainer's advice)
• Latest docs are also available in GitHub's main branch: https://github.com/unjs/c12

Existing projects depending on c12 <= v3:

• Might be better wait till c12@4.0.0 is tagged before upgrading or pin to the exact prerelease version
• The install size benefit is mainly if they can afford to require optional peer dependencies
• Rushing to migrate to a pinned beta version, likely adds to total install sizes due to multiple versions of c12 in node_modules (ecosystem-wise)

In general

dist-tags !== semver versions.

npm dist tags are human-readable, mutable labels, similar to GitHub branches.

npm versions are immutable and follow strict semver rules. pnpm add c12, it strictly pins to the exact version when the latest tag points to a prerelease semver.

---

I appreciate that you took the time to raise this question ❤️ I hope the notes above were clear enough.

I’m going to close and lock this discussion, as I don’t have the time or energy to continue it.