chore(e2e): retire vite trusted-publisher override#8526
Conversation
Bumps vite direct deps to ^7.3.3 across nine fixture templates and two
playground apps that were previously on vite 4/5/6/7.0, then drops the
corresponding entry from root pnpm.overrides and TRUSTED_OVERRIDES.
vite 7.1.3 is the first version published via OIDC trusted publisher.
@vitejs/plugin-react@^4 supports vite 4-7 so plugin versions don't need
to move. Fixture vite configs are minimal defineConfig({ plugins: [react()] })
and unaffected by 4→7 breaking changes.
🦋 Changeset detectedLatest commit: 7184866 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThis PR removes the global vite override from root pnpm.overrides and from TRUSTED_OVERRIDES, applies a uniform vite devDependency version (^7.3.3) across integration templates (with Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@integration/templates/vue-vite/package.json`:
- Around line 16-18: The package.json currently pins "@vitejs/plugin-vue":
"^5.1.4" which is incompatible with "vite": "^7.3.3"; update the dependency to a
version that supports Vite 7 (e.g. change "@vitejs/plugin-vue" to "^6.0.0" or
later) so the template can build with Vite 7.3.3 and regenerate/install
lockfiles as needed.
🪄 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: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: 29470f5d-3bb1-4c7f-ac13-5a8ff967c2f7
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (13)
.changeset/retire-vite-override.mdintegration/constants.tsintegration/templates/chrome-extension-vite/package.jsonintegration/templates/custom-flows-react-vite/package.jsonintegration/templates/express-vite/package.jsonintegration/templates/fastify-vite/package.jsonintegration/templates/hono-vite/package.jsonintegration/templates/react-router-library/package.jsonintegration/templates/react-vite/package.jsonintegration/templates/vue-vite/package.jsonpackage.jsonplayground/react-router/package.jsonplayground/vite-react-ts/package.json
💤 Files with no reviewable changes (1)
- integration/constants.ts
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
vite 7 declares peerOptional @types/node "^20.19.0 || >=22.12.0", which the react-vite template's ^18.19.33 pin fails under npm's strict resolution (pkglab uses npm internally). Bumps that template's @types/node to ^22.12.0. vue-vite was on @vitejs/plugin-vue ^5.1.4, which only supports vite 5/6. Bumps it to ^6.0.0 for vite 7 support.
# Conflicts: # integration/constants.ts # playground/react-router/package.json # playground/vite-react-ts/package.json # pnpm-lock.yaml
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.changeset/retire-vite-override.md:
- Around line 1-2: The changeset file .changeset/retire-vite-override.md is
empty but should either contain a release entry or be removed; update it to
include the appropriate changeset metadata: add one or more package bump blocks
(package name and bump type: patch/minor/major) plus a short summary describing
"Retire Vite override and standardize template dependency" so the PR produces a
changelog entry, or if this PR truly makes no release changes delete the file to
avoid an empty changeset.
🪄 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: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: 0d2a67b4-5320-4614-bd88-da5024fd6411
📒 Files selected for processing (1)
.changeset/retire-vite-override.md
Follow-up to #8522. Bumps
viteto^7.3.3across eight integration test templates and drops thevite@<7.1.3entry from rootpnpm.overridesandTRUSTED_OVERRIDES. vite 7.1.3 is the first version published via OIDC trusted publisher.Also aligns peer deps for vite 7: bumps
@types/nodeinreact-viteto^22.12.0(vite 7 declarespeerOptional @types/node "^20.19.0 || >=22.12.0", which npm-strict resolution in pkglab rejects under the older^18.19.33pin), and@vitejs/plugin-vueinvue-viteto^6.0.0(the ^5 line only supports vite 5/6).@vitejs/plugin-react@^4already covers vite 4-7 so plugin versions don't need to move. Fixture vite configs are minimaldefineConfig({ plugins: [react()] })and unaffected by 4→7 breaking changes.