chore: stop vitest bumps from releasing every package#2964
Merged
Conversation
A vitest bump (e.g. #2962) produced a changeset patch-bumping all 23 publishable packages. The chain: `racejar` peer-depends on vitest, so the update matched the `dependencies`/`peerDependencies` rule and the PR became `fix(deps)`; the changeset workflow (`mscharley/dependency-changesets-action`, conventional-commits mode) maps `fix` to a patch changeset and attributes the pnpm-catalog bump to every package consuming the catalog entry, which for test tooling is the entire workspace. Pin the vitest group to `semanticCommitType: chore`. The action maps anything but `fix`/`feat` to no changeset at all, so vitest updates no longer release-bump anything. The rule is last in `packageRules`, so it overrides the peer-dependencies `fix` rule for the vitest group. vitest is devDependencies everywhere except `racejar`'s peer range; suppressing that range bump's changeset is deliberate (a caret patch bump is not consumer-observable). A future vitest major that moves the peer range for real needs a manual changeset for `racejar`.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📦 Bundle Stats —
|
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 800.0 KB | - |
| Internal (gzip) | 153.3 KB | - |
| Bundled (raw) | 1.41 MB | - |
| Bundled (gzip) | 317.5 KB | - |
| Import time | 98ms | +1ms, +1.0% |
@portabletext/editor/behaviors
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 467 B | - |
| Internal (gzip) | 207 B | - |
| Bundled (raw) | 424 B | - |
| Bundled (gzip) | 171 B | - |
| Import time | 2ms | +0ms, +1.0% |
@portabletext/editor/plugins
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 2.7 KB | - |
| Internal (gzip) | 894 B | - |
| Bundled (raw) | 2.5 KB | - |
| Bundled (gzip) | 827 B | - |
| Import time | 7ms | -0ms, -0.0% |
@portabletext/editor/selectors
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 81.2 KB | - |
| Internal (gzip) | 14.9 KB | - |
| Bundled (raw) | 76.7 KB | - |
| Bundled (gzip) | 13.8 KB | - |
| Import time | 8ms | +0ms, +1.7% |
@portabletext/editor/traversal
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 28.1 KB | - |
| Internal (gzip) | 5.6 KB | - |
| Bundled (raw) | 27.9 KB | - |
| Bundled (gzip) | 5.5 KB | - |
| Import time | 6ms | -0ms, -1.2% |
@portabletext/editor/utils
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 29.7 KB | - |
| Internal (gzip) | 6.2 KB | - |
| Bundled (raw) | 27.1 KB | - |
| Bundled (gzip) | 5.8 KB | - |
| Import time | 6ms | +0ms, +0.2% |
🗺️ . · ./behaviors · ./plugins · ./selectors · ./traversal · ./utils · Artifacts
Details
- Import time regressions over 10% are flagged with
⚠️ - Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.
📦 Bundle Stats — @portabletext/markdown
Compared against main (f0eeb73b)
| Metric | Value | vs main (f0eeb73) |
|---|---|---|
| Internal (raw) | 53.8 KB | - |
| Internal (gzip) | 9.8 KB | - |
| Bundled (raw) | 348.9 KB | - |
| Bundled (gzip) | 96.3 KB | - |
| Import time | 39ms | -2ms, -4.6% |
🗺️ View treemap · Artifacts
Details
- Import time regressions over 10% are flagged with
⚠️ - Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.
`.changeset/dependencies-GH-2962.md` (merged with #2962) patch-bumps all 23 publishable packages for a vitest devDependency update; nothing any consumer installs changed. `racejar`'s vitest peer range moved `^4.1.9` -> `^4.1.10`, but an in-range floor ratchet is not consumer-observable either, so no package needs a release. Removing the changeset shrinks the pending Version Packages PR back to real changes.
christianhg
changed the title
chore so no changesets are generated
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renovate's vitest bump #2962 merged with a changeset that patch-bumps all 23 publishable packages, for a dev-tooling update that changes nothing any consumer installs. The pending Version Packages PR (#2963) is currently proposing exactly that release. This PR removes the merged changeset and prevents the next one.
The chain:
racejarpeer-depends on vitest, so the update matched thedependencies/peerDependenciespackageRule and the PR was titledfix(deps). The changeset workflow (mscharley/dependency-changesets-actionviaportabletext/.github, conventional-commits mode) mapsfixto a patch changeset, and it attributes the pnpm-catalog bump to every package that consumes the catalog entry, which for test tooling is the entire workspace. The action has no dep-type filtering inputs (v1.2.4 is current), so the only sanctioned lever is the commit type: it generates changesets only forfix/featand skips everything else.Commit 1 pins the existing vitest group rule to
semanticCommitType: chore. It's the last entry inpackageRules, so it overrides the peer-dependenciesfixrule for the vitest group; vitest PRs stop producing changesets entirely. Commit 2 deletes.changeset/dependencies-GH-2962.md, shrinking #2963 back to real changes.One deliberate suppression:
racejar's vitest peer range (^4.1.9→^4.1.10) also stops generating a changeset, and the merged ratchet ships silently with racejar's next real release. An in-range floor bump is not consumer-observable, so nothing is lost; if anything, releasing it would be mildly hostile (consumers on 4.1.9 would start failing strict peer resolution). A future vitest major that moves the peer range for real is a genuine manifest change and needs a manual changeset forracejar; majors are already gated behind dashboard approval.