build(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.3#25
build(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.3#25dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.2.0 to 6.0.3. - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.3/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by minimax-m3 · Input: 51.1K · Output: 5.5K · Cached: 545.4K |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d6a7e21af8
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@types/react-dom": "^19.2.3", | ||
| "@types/uuid": "^11.0.0", | ||
| "@vitejs/plugin-react": "^5.1.4", | ||
| "@vitejs/plugin-react": "^6.0.3", |
There was a problem hiding this comment.
Update the Bun lockfile for this dependency bump
Changing the root manifest without updating bun.lock leaves the lockfile at @vitejs/plugin-react ^5.1.4/5.2.0 (bun.lock lines 111 and 1136). The repo's CI and Docker builds run bun install --frozen-lockfile (.github/workflows/ci.yml line 46, docker/Dockerfile line 11), so this checkout no longer has a matching locked entry for ^6.0.3 and dependency installation has to resolve a new version instead of using the frozen lockfile. Regenerate and commit bun.lock with the manifest change.
Useful? React with 👍 / 👎.
| "@types/react-dom": "^19.2.3", | ||
| "@types/uuid": "^11.0.0", | ||
| "@vitejs/plugin-react": "^5.1.4", | ||
| "@vitejs/plugin-react": "^6.0.3", |
There was a problem hiding this comment.
Keep Vite on a supported major for plugin-react 6
@vitejs/plugin-react@6.0.3 declares a vite peer dependency of ^8.0.0, but this manifest still pins the app to vite ^7.3.1 on line 78. Once the lockfile is regenerated, the dev/build scripts that load vite.config.ts will run the React plugin against an unsupported Vite major (or force a duplicate peer install), so either bump Vite to 8 with this change or keep the React plugin on the 5.x line.
Useful? React with 👍 / 👎.
Bumps @vitejs/plugin-react from 5.2.0 to 6.0.3.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
640fd35release: plugin-react@6.0.3889efb0fix(deps): update all non-major dependencies (#1249)6c57dd4fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...3cc33a7fix(deps): update react-related dependencies (#1245)c0f7c7fdocs: mention the Biome rule in the "Consistent components exports" section (...cd80f0ffix(deps): update all non-major dependencies (#1241)e38accafix(deps): update all non-major dependencies (#1227)9a9bb26perf(react): improve react compiler preset so that slightly more modules are ...6535b55release: plugin-react@6.0.2bf0e43bfeat(react): whitelist debugging-options (#1189)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)