Skip to content

chore(deps): bump vite-plus to 0.1.21-alpha.7#3

Draft
fengmk2 wants to merge 2 commits into
developfrom
update-vite-plus-alpha-0.1.21-alpha.7
Draft

chore(deps): bump vite-plus to 0.1.21-alpha.7#3
fengmk2 wants to merge 2 commits into
developfrom
update-vite-plus-alpha-0.1.21-alpha.7

Conversation

@fengmk2

@fengmk2 fengmk2 commented May 13, 2026

Copy link
Copy Markdown
Owner

Summary

Bump vite-plus and related packages to alpha 0.1.21-alpha.7.

Updated where applicable:

  • vite-plus
  • vitest (alias to @voidzero-dev/vite-plus-test)
  • vite (alias to @voidzero-dev/vite-plus-core)
  • overrides / resolutions / pnpm.overrides / pnpm-workspace.yaml catalogs
  • minimumReleaseAgeExclude / minimumReleaseAgeExcludes configured for pnpm + bun

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this May 13, 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 the versions of vite and vite-plus to 0.1.21-alpha.7 in package.json and introduces a minimumReleaseAgeExclude configuration in pnpm-workspace.yaml. A review comment points out that minimumReleaseAgeExclude is likely placed in the wrong file, as it is not a documented field for pnpm-workspace.yaml and will not be recognized by pnpm or Bun; it is recommended to move this configuration to a supported location like .npmrc or package.json.

Comment thread pnpm-workspace.yaml
Comment on lines +8 to +10
minimumReleaseAgeExclude:
- vite-plus
- "@voidzero-dev/*"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The minimumReleaseAgeExclude configuration is likely in the wrong file and will not be recognized by the package managers mentioned in the PR description.

  • pnpm: This setting is typically configured in .npmrc (as minimum-release-age-exclude) or in package.json under the pnpm field. While pnpm 10 moved some workspace-wide settings (like onlyBuiltDependencies) to pnpm-workspace.yaml, this specific key is not currently documented as a supported field in the workspace file.
  • Bun: Bun does not read pnpm-workspace.yaml. It expects this configuration in bunfig.toml or package.json.

Consider moving this configuration to a supported location to ensure it functions as intended.

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