Skip to content

chore: upgrade Vitest catalog#1514

Merged
h4rkl merged 1 commit into
mainfrom
chore/vitest
Jun 3, 2026
Merged

chore: upgrade Vitest catalog#1514
h4rkl merged 1 commit into
mainfrom
chore/vitest

Conversation

@h4rkl

@h4rkl h4rkl commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add Vitest to the pnpm catalog at 4.1.8
  • switch direct workspace Vitest dev dependencies to catalog:
  • refresh the pnpm lockfile for Vitest 4.1.8

Test plan

  • pnpm test
  • pnpm list vitest -r --depth 0

@vercel

vercel Bot commented Jun 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
solana-com Ready Ready Preview, Comment Jun 3, 2026 9:13pm
solana-com-accelerate Ready Ready Preview, Comment Jun 3, 2026 9:13pm
solana-com-breakpoint-2 Ready Ready Preview, Comment Jun 3, 2026 9:13pm
solana-com-docs Ready Ready Preview, Comment Jun 3, 2026 9:13pm
solana-com-media Ready Ready Preview, Comment Jun 3, 2026 9:13pm
templates Ready Ready Preview, Comment Jun 3, 2026 9:13pm

Request Review

@greptile-apps

greptile-apps Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR standardizes Vitest across the monorepo by adding vitest: 4.1.8 to the pnpm workspace catalog and switching all six packages from individually pinned version ranges to catalog:. The lockfile consolidates what were two separate resolved versions (v2.1.9 and v4.0.18) into a single v4.1.8 entry.

  • packages/docs-examples makes the largest jump (v2.1.9 → v4.1.8), but its test files only use the stable describe/it/expect trio and its globalSetup module exports the standard setup/teardown shape, so no API-level breakage is expected.
  • All other packages move from ^4.0.18 to 4.1.8, a minor patch bump within the same major.
  • The lockfile correctly removes the stale @vitest/*@2.1.9 and @vitest/*@4.0.18 sub-package entries and introduces their 4.1.8 replacements.

Confidence Score: 5/5

Safe to merge — the change is a straightforward dependency consolidation with no logic modifications.

All six packages now resolve to a single vitest version via the catalog, eliminating version drift. The only package making a cross-major jump (docs-examples, v2 → v4) has tests that exclusively use the stable describe/it/expect surface; its globalSetup module exports the unchanged setup/teardown contract. The lockfile correctly drops all v2 and v4.0.x sub-packages.

No files require special attention.

Important Files Changed

Filename Overview
pnpm-workspace.yaml Adds vitest 4.1.8 to the catalog; no other changes
packages/docs-examples/package.json Major version bump from ^2.1.9 to catalog: (4.1.8); test files only use stable describe/it/expect APIs, no compatibility concern
apps/breakpoint/package.json Switches vitest from ^4.0.18 to catalog: (minor bump)
apps/media/package.json Switches vitest from ^4.0.18 to catalog: (minor bump)
apps/web/package.json Switches vitest from ^4.0.18 to catalog: (minor bump)
packages/i18n/package.json Switches vitest from ^4.0.18 to catalog: (minor bump)
packages/ui-chrome/package.json Switches vitest from ^4.0.18 to catalog: (minor bump)
pnpm-lock.yaml Lockfile updated to remove @vitest/* v2.1.9 and v4.0.18 entries, replaced by single v4.1.8 across all sub-packages

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pnpm-workspace.yaml\ncatalog: vitest 4.1.8] --> B[apps/breakpoint\ncatalog:]
    A --> C[apps/media\ncatalog:]
    A --> D[apps/web\ncatalog:]
    A --> E[packages/docs-examples\ncatalog:]
    A --> F[packages/i18n\ncatalog:]
    A --> G[packages/ui-chrome\ncatalog:]

    B -. "was ^4.0.18" .-> H[pnpm-lock.yaml\nresolved: 4.1.8]
    C -. "was ^4.0.18" .-> H
    D -. "was ^4.0.18" .-> H
    E -. "was ^2.1.9" .-> H
    F -. "was ^4.0.18" .-> H
    G -. "was ^4.0.18" .-> H
Loading

Reviews (1): Last reviewed commit: "chore: upgrade vitest catalog" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant