chore: Upgrade vite to 7.3.2 instead of 7.3.1 by kingston · Pull Request #883 · halfdomelabs/baseplate

kingston · 2026-04-07T12:13:52Z

Summary by CodeRabbit

Chores
- Updated Vite build tool to version 7.3.2 across all project packages and configurations.

changeset-bot · 2026-04-07T12:13:57Z

⚠️ No Changeset found

Latest commit: bed57c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 24 packages

Name	Type
@baseplate-dev/core-generators	Patch
@baseplate-dev/react-generators	Patch
@baseplate-dev/fastify-generators	Patch
@baseplate-dev/project-builder-server	Patch
@baseplate-dev/plugin-ai	Patch
@baseplate-dev/plugin-auth	Patch
@baseplate-dev/plugin-email	Patch
@baseplate-dev/plugin-observability	Patch
@baseplate-dev/plugin-payments	Patch
@baseplate-dev/plugin-queue	Patch
@baseplate-dev/plugin-rate-limit	Patch
@baseplate-dev/plugin-storage	Patch
@baseplate-dev/create-project	Patch
@baseplate-dev/project-builder-cli	Patch
@baseplate-dev/project-builder-common	Patch
@baseplate-dev/project-builder-dev	Patch
@baseplate-dev/project-builder-web	Patch
@baseplate-dev/project-builder-test	Patch
@baseplate-dev/code-morph	Patch
@baseplate-dev/project-builder-lib	Patch
@baseplate-dev/sync	Patch
@baseplate-dev/tools	Patch
@baseplate-dev/ui-components	Patch
@baseplate-dev/utils	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai · 2026-04-07T12:14:10Z

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1cbc2e40-beb0-4eca-a4d8-63a737095821

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Vite from version 7.3.1 to 7.3.2 across the codebase, including example applications, package generator constants, and workspace configuration. The change also excludes Vite from the minimum release age constraint in pnpm-workspace.yaml.

Changes

Cohort / File(s)	Summary
Release Notes `.changeset/upgrade-vite-to-7-3-2.md`	Updated changeset documenting Vite version bump from 7.3.1 to 7.3.2.
Example App Dependencies `examples/blog-with-auth/apps/admin/package.json`, `examples/blog-with-auth/apps/backend/package.json`, `examples/blog-with-auth/libs/transactional/package.json`, `examples/todo-with-better-auth/apps/admin/package.json`, `examples/todo-with-better-auth/apps/backend/package.json`, `examples/todo-with-better-auth/apps/web/package.json`, `examples/todo-with-better-auth/libs/transactional/package.json`	Updated Vite devDependency from 7.3.1 to 7.3.2 across all example applications and libraries.
Package Generator Constants `packages/core-generators/src/constants/core-packages.ts`, `packages/react-generators/src/constants/react-packages.ts`	Updated pinned Vite version in package constant definitions from 7.3.1 to 7.3.2.
Workspace Configuration `pnpm-workspace.yaml`	Updated Vite version in dependency catalog from 7.3.1 to 7.3.2 and added Vite to `minimumReleaseAgeExclude` to exclude it from the 1440-minute release age constraint.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

feat: Upgrade vite to 7.1.12 #685: Updates pinned Vite versions across the same files (package.json entries and generator constants) and pnpm-workspace.yaml.
chore: Upgrade vitest to 3.0.7 and vite to 6.2.0 #441: Modifies Vite version pins in core-packages.ts, react-packages.ts, and related package.json entries.
chore: Upgrade vite version from 7.1.12 to 7.3.1 #882: Performs similar Vite version updates across the same configuration files and constants.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: upgrading Vite from version 7.3.1 to 7.3.2 across the entire codebase.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch kingston/upgrade-vite-to-7.3.2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (1)

pnpm-workspace.yaml (1)
42-44: Consider time-bounding the minimumReleaseAgeExclude for vite.

This exception is reasonable for an urgent bump, but it can weaken supply-chain guardrails if left indefinitely. Consider adding a short comment/TODO with removal criteria.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@pnpm-workspace.yaml` around lines 42 - 44, The entry under
minimumReleaseAgeExclude that lists "vite" should be time-bounded and
documented: update the pnpm-workspace.yaml to add a short inline comment/TODO
next to the vite exclusion indicating why it was added, the specific removal
criteria (e.g., date or resolved issue/PR number), and a target expiry (e.g.,
30/60/90 days); ensure the comment references the minimumReleaseAgeExclude key
and the "vite" value so reviewers can easily find and remove the exception when
the criteria are met.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/upgrade-vite-to-7-3-2.md:
- Line 6: Update the changeset description line that currently reads "Upgrade
vite version from 7.1.12 to 7.3.2" to the correct source version "Upgrade vite
version from 7.3.1 to 7.3.2" in the .changeset/upgrade-vite-to-7-3-2.md file so
the released notes match the PR scope; locate and edit the literal string in
that file to reflect 7.3.1 -> 7.3.2.

---

Nitpick comments:
In `@pnpm-workspace.yaml`:
- Around line 42-44: The entry under minimumReleaseAgeExclude that lists "vite"
should be time-bounded and documented: update the pnpm-workspace.yaml to add a
short inline comment/TODO next to the vite exclusion indicating why it was
added, the specific removal criteria (e.g., date or resolved issue/PR number),
and a target expiry (e.g., 30/60/90 days); ensure the comment references the
minimumReleaseAgeExclude key and the "vite" value so reviewers can easily find
and remove the exception when the criteria are met.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0ea5e3d0-30bb-48c5-ab6c-4082677e29f7

📥 Commits

Reviewing files that changed from the base of the PR and between cfb3bb1 and f0e5dba.

⛔ Files ignored due to path filters (11)

examples/blog-with-auth/apps/admin/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/blog-with-auth/apps/backend/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/blog-with-auth/libs/transactional/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/blog-with-auth/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
examples/todo-with-better-auth/apps/admin/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/todo-with-better-auth/apps/backend/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/todo-with-better-auth/apps/web/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/todo-with-better-auth/libs/transactional/baseplate/generated/package.json is excluded by !**/generated/**, !**/generated/**
examples/todo-with-better-auth/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
tests/simple/snapshots/root/diffs/pnpm-lock.yaml.diff is excluded by !tests/**

📒 Files selected for processing (11)

.changeset/upgrade-vite-to-7-3-2.md
examples/blog-with-auth/apps/admin/package.json
examples/blog-with-auth/apps/backend/package.json
examples/blog-with-auth/libs/transactional/package.json
examples/todo-with-better-auth/apps/admin/package.json
examples/todo-with-better-auth/apps/backend/package.json
examples/todo-with-better-auth/apps/web/package.json
examples/todo-with-better-auth/libs/transactional/package.json
packages/core-generators/src/constants/core-packages.ts
packages/react-generators/src/constants/react-packages.ts
pnpm-workspace.yaml

coderabbitai · 2026-04-07T12:18:18Z

 ---

-Upgrade vite version from 7.1.12 to 7.3.1
+Upgrade vite version from 7.1.12 to 7.3.2


⚠️ Potential issue | 🟡 Minor

Fix the source version in the changeset description.

The description says 7.1.12 -> 7.3.2, but this PR is scoped to 7.3.1 -> 7.3.2. Please align the text to avoid misleading release notes.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In @.changeset/upgrade-vite-to-7-3-2.md at line 6, Update the changeset description line that currently reads "Upgrade vite version from 7.1.12 to 7.3.2" to the correct source version "Upgrade vite version from 7.3.1 to 7.3.2" in the .changeset/upgrade-vite-to-7-3-2.md file so the released notes match the PR scope; locate and edit the literal string in that file to reflect 7.3.1 -> 7.3.2.

chore: Upgrade vite to 7.3.2 instead of 7.3.1

f0e5dba

coderabbitai Bot reviewed Apr 7, 2026

View reviewed changes

Run pnpm dedupe

bed57c0

kingston merged commit b231bca into main Apr 7, 2026
12 checks passed

kingston deleted the kingston/upgrade-vite-to-7.3.2 branch April 7, 2026 13:18

github-actions Bot mentioned this pull request Apr 7, 2026

chore: Version Packages #879

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: Upgrade vite to 7.3.2 instead of 7.3.1#883

chore: Upgrade vite to 7.3.2 instead of 7.3.1#883
kingston merged 2 commits into
mainfrom
kingston/upgrade-vite-to-7.3.2

kingston commented Apr 7, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

changeset-bot Bot commented Apr 7, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Apr 7, 2026 •

edited

Loading

Review skipped

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Apr 7, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

kingston commented Apr 7, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

changeset-bot Bot commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

coderabbitai Bot commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

kingston commented Apr 7, 2026 •

edited by coderabbitai Bot

Loading

changeset-bot Bot commented Apr 7, 2026 •

edited

Loading

coderabbitai Bot commented Apr 7, 2026 •

edited

Loading