Skip to content

chore(deps): update dependency vite to v8 - autoclosed#213

Closed
renovate[bot] wants to merge 1 commit intotrunkfrom
renovate/vite-8.x
Closed

chore(deps): update dependency vite to v8 - autoclosed#213
renovate[bot] wants to merge 1 commit intotrunkfrom
renovate/vite-8.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 23, 2026

This PR contains the following updates:

Package Change Age Confidence
vite (source) 7.3.18.0.3 age confidence

Release Notes

vitejs/vite (vite)

v8.0.3

Compare Source

Features
Bug Fixes
  • html: cache unfiltered CSS list to prevent missing styles across entries (#​22017) (5464190)
  • module-runner: handle non-ascii characters in base64 sourcemaps (#​21985) (77c95bf)
  • module-runner: skip re-import if the runner is closed (#​22020) (ee2c2cd)
  • optimizer: scan is not resolving sub path import if used in a glob import (#​22018) (ddfe20d)
  • ssr: ssrTransform incorrectly rewrites meta identifier inside import.meta when a binding named meta exists (#​22019) (cff5f0c)
Miscellaneous Chores
Tests

v8.0.2

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.0

Compare Source

Features
Bug Fixes

v7.3.2

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

@socket-security
Copy link
Copy Markdown

socket-security bot commented Mar 23, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedvite@​8.0.3941008298100

View full report

@socket-security
Copy link
Copy Markdown

socket-security bot commented Mar 23, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm vite is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: package.jsonnpm/vite@8.0.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@8.0.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate renovate bot force-pushed the renovate/vite-8.x branch 2 times, most recently from ef96bf9 to e0c7543 Compare March 30, 2026 17:50
@renovate renovate bot force-pushed the renovate/vite-8.x branch from e0c7543 to d872943 Compare April 2, 2026 09:46
@renovate renovate bot changed the title chore(deps): update dependency vite to v8 chore(deps): update dependency vite to v8 - autoclosed Apr 7, 2026
@renovate renovate bot closed this Apr 7, 2026
@renovate renovate bot deleted the renovate/vite-8.x branch April 7, 2026 00:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants