Skip to content

chore(deps): bump vite-plus to v0.2.0 - #3

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

chore(deps): bump vite-plus to v0.2.0#3
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-prerelease-test-0.2.0

Conversation

@fengmk2

@fengmk2 fengmk2 commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

Bump vite-plus and related packages to the pkg.pr.new prerelease build for v0.2.0.

Updated where applicable:

  • vite-plus -> pkg.pr.new build
  • vite (alias/override -> @voidzero-dev/vite-plus-core)
  • vitest pinned to bundled 4.1.9 (the @voidzero-dev/vite-plus-test wrapper was removed upstream; vitest is now plain upstream)
  • minimumReleaseAge enabled with vite-plus packages excluded (pnpm/bun/npm as applicable)

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this Jun 17, 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 updates dependency versions across package.json, pnpm-lock.yaml, and pnpm-workspace.yaml, upgrading @vitest/coverage-v8 to 4.1.9 and pinning vite-plus and related packages to specific PR builds. A critical issue was identified in pnpm-workspace.yaml where several .npmrc configurations, such as blockExoticSubdeps and minimumReleaseAge, were incorrectly placed and will be ignored by pnpm. These settings should be moved to the root .npmrc file using the correct kebab-case format.

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 +15 to +27
blockExoticSubdeps: false
minimumReleaseAge: 60
minimumReleaseAgeExclude:
- "@voidzero-dev/*"
- vite-plus
- "@vitest/*"
- vite
- vitest
- "@oxc-project/*"
- "@oxlint/*"
- oxlint
- oxfmt
- oxlint-tsgolint

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

Misplaced .npmrc Configurations in pnpm-workspace.yaml\n\nThe configurations blockExoticSubdeps, minimumReleaseAge, and minimumReleaseAgeExclude are .npmrc settings (specifically block-exotic-subdeps, minimum-release-age, and minimum-release-age-exclude in pnpm).\n\npnpm does not read these settings from pnpm-workspace.yaml. Leaving them here will result in them being completely ignored, meaning the minimum release age and exotic subdependency blocking features will not be active.\n\n### Solution\n1. Remove these lines from pnpm-workspace.yaml.\n2. Add them to your .npmrc file at the root of the project using the correct kebab-case format:\n\nini\nblock-exotic-subdeps=false\nminimum-release-age=60\nminimum-release-age-exclude[]=@voidzero-dev/*\nminimum-release-age-exclude[]=vite-plus\nminimum-release-age-exclude[]=@vitest/*\nminimum-release-age-exclude[]=vite\nminimum-release-age-exclude[]=vitest\nminimum-release-age-exclude[]=@oxc-project/*\nminimum-release-age-exclude[]=@oxlint/*\nminimum-release-age-exclude[]=oxlint\nminimum-release-age-exclude[]=oxfmt\nminimum-release-age-exclude[]=oxlint-tsgolint\n

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