fic/server
1
0
Fork 0
Code Issues Pull Requests10 Releases Wiki Activity

chore(deps): update dependency vite to v5.4.17 #546

Open
renovate-bot wants to merge 1 commits from renovate/vite-5.x-lockfile into master
Conversation 0 Commits 1 Files Changed 2 +6 -7
renovate-bot commented 2025-03-31 11:19:03 +00:00
Collaborator

This PR contains the following updates:

Package Type Update Change
vite (source) devDependencies patch 5.4.15 -> 5.4.17
vite (source) dependencies patch 5.4.15 -> 5.4.17

Release Notes

vitejs/vite (vite)

v5.4.17

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.16

Compare Source

Please refer to CHANGELOG.md for details.

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 these updates again.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [vite](https://vite.dev) ([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) | devDependencies | patch | [`5.4.15` -> `5.4.17`](https://renovatebot.com/diffs/npm/vite/5.4.15/5.4.17) | | [vite](https://vite.dev) ([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) | dependencies | patch | [`5.4.15` -> `5.4.17`](https://renovatebot.com/diffs/npm/vite/5.4.15/5.4.17) | --- ### Release Notes <details> <summary>vitejs/vite (vite)</summary> ### [`v5.4.17`](https://github.com/vitejs/vite/releases/tag/v5.4.17) [Compare Source](https://github.com/vitejs/vite/compare/v5.4.16...v5.4.17) Please refer to [CHANGELOG.md](https://github.com/vitejs/vite/blob/v5.4.17/packages/vite/CHANGELOG.md) for details. ### [`v5.4.16`](https://github.com/vitejs/vite/releases/tag/v5.4.16) [Compare Source](https://github.com/vitejs/vite/compare/v5.4.15...v5.4.16) Please refer to [CHANGELOG.md](https://github.com/vitejs/vite/blob/v5.4.16/packages/vite/CHANGELOG.md) for details. </details> --- ### 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNjQuMSIsInVwZGF0ZWRJblZlciI6IjM5LjE2NC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate-bot added 1 commit 2025-03-31 11:19:05 +00:00
renovate-bot force-pushed renovate/vite-5.x-lockfile from f847259bef to 178c99263a 2025-04-01 11:19:41 +00:00 Compare
renovate-bot force-pushed renovate/vite-5.x-lockfile from 178c99263a to e7c49b64fe 2025-04-03 11:26:01 +00:00 Compare
renovate-bot changed title from chore(deps): update dependency vite to v5.4.16 to chore(deps): update dependency vite to v5.4.17 2025-04-03 11:26:11 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/vite-5.x-lockfile:renovate/vite-5.x-lockfile
git checkout renovate/vite-5.x-lockfile
Sign in to join this conversation.
No Reviewers
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fic/server#546
No description provided.
Delete Branch "renovate/vite-5.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?