feat: Update some dependencies#12811
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f1265b42e2
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "unplugin-auto-import": "^0.16.7", | ||
| "unplugin-vue-components": "^0.25.2", | ||
| "vite": "^7.3.2", | ||
| "vite": "^8.0.13", |
There was a problem hiding this comment.
Upgrading vite to ^8.0.13 without upgrading the Vue Vite plugins leaves the toolchain in an unsupported combination (@vitejs/plugin-vue@6.0.2 and @vitejs/plugin-vue-jsx@5.1.2 both declare peers up to Vite 7). In this repo, running npm install --package-lock-only --ignore-scripts in frontend/ reports peer-resolution warnings for this exact mismatch, so builds may become unstable or fail depending on npm settings/CI strictness.
Useful? React with 👍 / 👎.
| "monaco-editor": "^0.53.0", | ||
| "nprogress": "^0.2.0", | ||
| "pinia": "^2.1.7", | ||
| "pinia": "^3.0.4", |
There was a problem hiding this comment.
Bumping pinia to ^3.0.4 while keeping pinia-plugin-persistedstate on the 1.x line introduces a peer mismatch (pinia-plugin-persistedstate@1.6.3 declares pinia: ^2.0.0). The same npm install --package-lock-only --ignore-scripts run in frontend/ surfaces this conflict, which risks persistence hooks failing at runtime or install failures in stricter environments.
Useful? React with 👍 / 👎.
3 participants
No description provided.