chore(deps): update dependency vite to v7.2.4 #107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/vite-7.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.1.12->7.2.4Release Notes
vitejs/vite (vite)
v7.2.4Compare Source
Bug Fixes
v7.2.3Compare Source
Bug Fixes
bindCLIShortcutscalls with shortcut merging (#21103) (5909efd)Performance Improvements
Miscellaneous Chores
v7.2.2Compare Source
Bug Fixes
v7.2.1Compare Source
Bug Fixes
Code Refactoring
indexOfMatchInSlicetofindPreloadMarker(#21054) (f83264f)v7.2.0Compare Source
Bug Fixes
getBuiltinsresponse JSON serializable (#21029) (ad5b3bf)Miscellaneous Chores
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: yarn.lock
2176b2b5527d792030b77d792030b7d1568a47f9d1568a47f9c6db31922bchore(deps): update dependency vite to v7.2.0to chore(deps): update dependency vite to v7.2.1c6db31922b3d021ab5f6chore(deps): update dependency vite to v7.2.1to chore(deps): update dependency vite to v7.2.23d021ab5f6291b09f152291b09f152d4be39f4f2d4be39f4f28b2ae8d2adchore(deps): update dependency vite to v7.2.2to chore(deps): update dependency vite to v7.2.4View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.