| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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>
Codecov Report✅ All modified and coverable lines are covered by tests. @@ 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. |
Sorry, something went wrong.
| "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)
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 FixUpdate 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 AgentFix 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.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps vite from 6.3.5 to 7.1.11.
Release notesSourced from vite's releases.
... (truncated)
ChangelogSourced from vite's changelog.
... (truncated)
Commits- 8b69c9e release: v7.1.11
- f479cc5 fix(dev): trim trailing slash before server.fs.deny check (#20968)
- 6fb41a2 chore(deps): update all non-major dependencies (#20966)
- a817307 build: remove hash from built filenames (#20946)
- ef411ce build: remove cjs reference in files field (#20945)
- d0094af refactor: use subpath imports for types module reference (#20921)
- ed4a0dc release: v7.1.10
- c714776 fix: preserve original sourcemap file field when combining sourcemaps (#20926)
- 446eb38 fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20906)
- 879de86 fix(deps): update all non-major dependencies
- Additional commits viewable in compare view
Maintainer changesThis 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:
You can disable automated security fix PRs for this repo from the Security Alerts page.