James Anderson
584661f37f
Changesets' shouldBumpMajor rule force-bumps a dependent to MAJOR when a peerDependency receives any non-patch bump. Combined with workspace:* being resolved as an exact version pin (always out of range on any vinext change), @vinext/cloudflare was majored on essentially every release (e.g. 0.0.1 -> 1.0.0 in PR #1759), even with zero cloudflare changes. Fix is two parts: - .changeset/config.json: enable onlyUpdatePeerDependentsWhenOutOfRange so peer-dependent bumps respect the declared range instead of force-majoring. - packages/cloudflare/package.json: widen the published peer range off the exact-pin (workspace:* -> >=0.0.0). devDependencies.vinext: workspace:* is kept so local linking is unaffected.
Changesets
Hello and welcome! This folder has been automatically generated by
@changesets/cli, a build tool that works with multi-package repos, or
single-package repos to help you version and publish your code. You can find the
full documentation for it
in our repository.
We have a quick list of common questions to get you started engaging with this project in our documentation.
Auto-generated changesets in CI
In this repo, most changesets are generated automatically from Conventional
Commits by scripts/create-changeset.mts during CI (see
.github/workflows/release.yml). Those auto-generated files are named
auto-*.md, are written only into the CI working tree, and are never
committed to main — they exist just long enough for changesets/action to
consume them into the rolling "Version Packages" PR.
You can still author changesets by hand. A human-committed .changeset/*.md on
main is honored exactly like normal: it is consumed alongside the
auto-generated ones when the Version PR is built. Add one with pnpm changeset
(or vp exec changeset) whenever you want to override or supplement the
commit-driven bump.