Skip to content

Conversation

@jcdc-bot
Copy link
Collaborator

snyk-top-banner

Snyk has created this PR to upgrade vite from 7.1.11 to 7.1.12.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 23 days ago.

Release notes
Package name: vite from vite GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade vite from 7.1.11 to 7.1.12.

See this package in npm:
vite

See this project in Snyk:
https://app.snyk.io/org/jcdcdev/project/3d466729-9b2e-402f-ab33-ae586fe880c8?utm_source=github&utm_medium=referral&page=upgrade-pr
@jcdc-bot
Copy link
Collaborator Author

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@jcdcdev jcdcdev merged commit fc30ad1 into dev/v16 Nov 15, 2025
3 checks passed
@github-actions github-actions bot changed the title [Snyk] Upgrade vite from 7.1.11 to 7.1.12 16.0.5-alpha0004 Nov 15, 2025
@github-actions github-actions bot added the ✅ released Indicates that the release has been successfully published. label Nov 15, 2025
@github-actions github-actions bot changed the title 16.0.5-alpha0004 16.0.5-alpha0004 (released) Nov 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✅ released Indicates that the release has been successfully published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants