chore(deps): bump vite from 6.3.5 to 7.1.11#127
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 7.1.11. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.11/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.1.11 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #127 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 8 8
Branches 5 5
=========================================
Hits 8 8 ☔ View full report in Codecov by Sentry. |
![seer-by-sentry[bot]](https://avatars.githubusercontent.com/in/801464?s=60&v=4){kind=small}
| "engines": { | ||
| "node": "^18.0.0 || ^20.0.0 || >=22.0.0" | ||
| "node": "^20.19.0 || >=22.12.0" | ||
| }, |
There was a problem hiding this comment.
Bug: The Vite 7.1.11 upgrade requires Node 20+, but the CI workflow runs on Node 18, which will cause npm install to fail.
(Severity: Critical 0.85 | Confidence: 1.00)
🔍 Detailed Analysis
The GitHub Actions workflow is configured to use Node 18. The update to Vite 7.1.11 introduces a stricter engine requirement of Node ^20.19.0 || >=22.12.0. When npm install is executed in the CI environment, npm will detect this version mismatch and raise an EBADENGINE error. This will cause the dependency installation to fail, breaking the entire CI/CD pipeline.
💡 Suggested Fix
Update the GitHub Actions workflow (ci.yml) to use a Node.js version compatible with Vite 7.1.11, such as version 20 or 22. Additionally, consider adding an engines field to package.json to enforce the Node version requirement across all environments.
🤖 Prompt for AI Agent
Fix this bug. In package-lock.json at line 1887: The GitHub Actions workflow is
configured to use Node 18. The update to Vite 7.1.11 introduces a stricter engine
requirement of Node `^20.19.0 || >=22.12.0`. When `npm install` is executed in the CI
environment, npm will detect this version mismatch and raise an `EBADENGINE` error. This
will cause the dependency installation to fail, breaking the entire CI/CD pipeline.
Did we get this right? 👍 / 👎 to inform future reviews.
Bumps vite from 6.3.5 to 7.1.11.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
8b69c9erelease: v7.1.11f479cc5fix(dev): trim trailing slash beforeserver.fs.denycheck (#20968)6fb41a2chore(deps): update all non-major dependencies (#20966)a817307build: remove hash from built filenames (#20946)ef411cebuild: remove cjs reference in files field (#20945)d0094afrefactor: use subpath imports for types module reference (#20921)ed4a0dcrelease: v7.1.10c714776fix: preserve original sourcemap file field when combining sourcemaps (#20926)446eb38fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20906)879de86fix(deps): update all non-major dependenciesMaintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vite since your current version.
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)You can disable automated security fix PRs for this repo from the Security Alerts page.