Nodarx/server
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

chore(deps): update dependency vite to v7 - autoclosed #10

Closed
Sebastian wants to merge 1 commits from renovate/vite-7.x into main
pull from: renovate/vite-7.x
merge into: Nodarx:main
Conversation 1 Commits 1 Files Changed 1 +1 -1
Sebastian commented 2026-02-11 05:50:38 +00:00
Owner
Copy Link

This PR contains the following updates:

Package Change Age Confidence
vite (source) 6.0.6 → 7.3.1 age confidence

❗ Important

Release Notes retrieval for this PR were skipped because no github.com credentials were available.
If you are self-hosted, please see this instruction.

Configuration

📅 Schedule: Branch creation - "before 3am" (UTC), 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.

  • 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 | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [vite](https://vite.dev) ([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) | [`6.0.6` → `7.3.1`](https://renovatebot.com/diffs/npm/vite/6.0.6/7.3.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/vite/7.3.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/6.0.6/7.3.1?slim=true) | > :exclamation: **Important** > > Release Notes retrieval for this PR were skipped because no github.com credentials were available. > If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **Schedule**: Branch creation - "before 3am" (UTC), 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. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0My44LjEiLCJ1cGRhdGVkSW5WZXIiOiI0My44LjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
Sebastian added 1 commit 2026-02-11 05:50:38 +00:00
chore(deps): update dependency vite to v7
Some checks failed
renovate/artifacts Artifact file update failure
Build Test / build (pull_request) Failing after 9s
Details
e4cf097633
Sebastian commented 2026-02-11 05:50:38 +00:00
Author
Owner
Copy Link

⚠️ 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitejs/plugin-vue@5.2.1
npm error Found: vite@7.3.1
npm error node_modules/vite
npm error   dev vite@"7.3.1" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from vite-plugin-static-copy@3.1.2
npm error   node_modules/vite-plugin-static-copy
npm error     dev vite-plugin-static-copy@"^3.1.2" from the root project
npm error   1 more (vite-plugin-vuetify)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.1
npm error node_modules/@vitejs/plugin-vue
npm error   dev @vitejs/plugin-vue@"5.2.1" from the root project
npm error
npm error Conflicting peer dependency: vite@6.4.1
npm error node_modules/vite
npm error   peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.1
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"5.2.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-02-11T05_57_45_279Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-02-11T05_57_45_279Z-debug-0.log
### ⚠️ 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: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: @vitejs/plugin-vue@5.2.1 npm error Found: vite@7.3.1 npm error node_modules/vite npm error dev vite@"7.3.1" from the root project npm error peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from vite-plugin-static-copy@3.1.2 npm error node_modules/vite-plugin-static-copy npm error dev vite-plugin-static-copy@"^3.1.2" from the root project npm error 1 more (vite-plugin-vuetify) npm error npm error Could not resolve dependency: npm error peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.1 npm error node_modules/@vitejs/plugin-vue npm error dev @vitejs/plugin-vue@"5.2.1" from the root project npm error npm error Conflicting peer dependency: vite@6.4.1 npm error node_modules/vite npm error peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.1 npm error node_modules/@vitejs/plugin-vue npm error dev @vitejs/plugin-vue@"5.2.1" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-02-11T05_57_45_279Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-02-11T05_57_45_279Z-debug-0.log ```
Sebastian force-pushed renovate/vite-7.x from e4cf097633 to ff2ac8567b 2026-02-11 05:57:49 +00:00 Compare
Sebastian changed title from chore(deps): update dependency vite to v7 to chore(deps): update dependency vite to v7 - autoclosed 2026-02-11 06:30:07 +00:00
Sebastian closed this pull request 2026-02-11 06:30:07 +00:00
Some checks failed
renovate/artifacts Artifact file update failure
Build Test / build (pull_request) Failing after 15s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Nodarx/server#10
Delete Branch "renovate/vite-7.x"

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?