Skip to content

chore(deps): bump vite-plus to v0.2.2#11

Draft
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-prerelease-test-0.2.2
Draft

chore(deps): bump vite-plus to v0.2.2#11
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-prerelease-test-0.2.2

Conversation

@fengmk2

@fengmk2 fengmk2 commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Summary

Bump vite-plus and related packages to the pkg.pr.new prerelease build for v0.2.2 (registry-bridge commit build) to smoke-test the prerelease.

  • vite-plus + vite (alias to @voidzero-dev/vite-plus-core) and vitest pinned to the commit build across deps / overrides / catalogs
  • minimumReleaseAge enabled with the vite-plus / @voidzero-dev/* / oxc / oxlint stack excluded
  • .npmrc (or .yarnrc.yml) points the package manager at the registry bridge (prerelease scaffolding)

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this Jul 2, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a registry bridge to .npmrc and updates pnpm-workspace.yaml with release age exclusions and pinned versions for vite, vite-plus, and vitest. The feedback suggests adding an overrides block to pnpm-workspace.yaml to ensure workspace-wide dependency resolution consistency and prevent duplicate installations or runtime conflicts.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread pnpm-workspace.yaml
Comment on lines 18 to +21
catalog:
vite: npm:@voidzero-dev/vite-plus-core@^0.1.21
vite-plus: ^0.1.21
vitest: npm:@voidzero-dev/vite-plus-test@^0.1.21
vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
vite-plus: 0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
vitest: 4.1.9

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The PR description mentions pinning vite and vitest to the commit build across overrides, but the overrides section is missing from pnpm-workspace.yaml. Without workspace-wide overrides, other packages in the dependency tree (such as @tailwindcss/vite or @vitejs/plugin-react) will resolve vite to the standard npm package instead of @voidzero-dev/vite-plus-core. This can lead to duplicate installations and runtime conflicts.

Adding the overrides block pointing to the catalog: versions ensures that all packages in the workspace consistently resolve to the Vite+ core and bundled Vitest versions.

catalog:
  vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
  vite-plus: 0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
  vitest: 4.1.9
overrides:
  vite: catalog:
  vitest: catalog:

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