Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency vite to v6 #1762

Closed
wants to merge 2 commits into from
Closed

fix(deps): update dependency vite to v6 #1762

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2024 •
edited by github-actions bot
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^5.2.8 -> ^6.0.0 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v6.0.6

Compare Source

v6.0.5

Compare Source

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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

This PR was generated by Mend Renovate. View the repository job log.

Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:

@renovate renovate bot enabled auto-merge (squash) December 3, 2024 09:55
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Dec 3, 2024 •
edited
Loading

⚠️ 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitejs/[email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   vite@"^6.0.0" from the root project
npm error   peer vite@">=4 <=6" from [email protected]
npm error   node_modules/vite-plugin-istanbul
npm error     vite-plugin-istanbul@"6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.2.0 || ^5.0.0" from @vitejs/[email protected]
npm error node_modules/@vitejs/plugin-react
npm error   @vitejs/plugin-react@"^4.0.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^4.2.0 || ^5.0.0" from @vitejs/[email protected]
npm error   node_modules/@vitejs/plugin-react
npm error     @vitejs/plugin-react@"^4.0.4" 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/2025-01-03T20_18_20_634Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-03T20_18_20_634Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vite branch 8 times, most recently from 1925631 to 9878eae Compare December 10, 2024 19:37
@renovate renovate bot force-pushed the renovate/major-vite branch 2 times, most recently from b68d3e0 to c2c6995 Compare December 20, 2024 01:01
@renovate renovate bot force-pushed the renovate/major-vite branch 2 times, most recently from 8e76822 to 86898d2 Compare January 3, 2025 00:56
@renovate renovate bot force-pushed the renovate/major-vite branch from 86898d2 to 8df8cf1 Compare January 3, 2025 20:18
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 3, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

auto-merge was automatically disabled January 3, 2025 20:59

Pull request was closed

@xiaopeng0202 xiaopeng0202 reopened this Jan 3, 2025
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 3, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-vite branch January 3, 2025 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@xiaopeng0202 xiaopeng0202 Awaiting requested review from xiaopeng0202 xiaopeng0202 is a code owner

@mgaseta mgaseta Awaiting requested review from mgaseta mgaseta is a code owner

@DerekRoberts DerekRoberts Awaiting requested review from DerekRoberts DerekRoberts is a code owner

@SLDonnelly SLDonnelly Awaiting requested review from SLDonnelly SLDonnelly is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@xiaopeng0202