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.

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

Update dependency vite to v5.2.10 - autoclosed #267

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 5.2.6 -> 5.2.10 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v5.2.10

Compare Source

v5.2.9

Compare Source

v5.2.8

Compare Source

v5.2.7

Compare Source


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.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

vercel bot commented Mar 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
todone ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 29, 2024 9:04am
todone-hosted ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 29, 2024 9:04am

@renovate renovate bot force-pushed the renovate/vite-5.x-lockfile branch from 71bf587 to 45f5006 Compare March 20, 2024 10:27
@renovate renovate bot changed the title Update dependency vite to v5.2.0 Update dependency vite to v5.2.2 Mar 20, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.2 Update dependency vite to v5.2.3 Mar 22, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.3 Update dependency vite to v5.2.4 Mar 23, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.4 Update dependency vite to v5.2.5 Mar 24, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.5 Update dependency vite to v5.2.6 Mar 24, 2024
@renovate renovate bot force-pushed the renovate/vite-5.x-lockfile branch from 45f5006 to fc207ff Compare March 27, 2024 09:41
@renovate renovate bot changed the title Update dependency vite to v5.2.6 Update dependency vite to v5.2.6 - autoclosed Mar 27, 2024
@renovate renovate bot closed this Mar 27, 2024
@renovate renovate bot deleted the renovate/vite-5.x-lockfile branch March 27, 2024 09:59
@renovate renovate bot changed the title Update dependency vite to v5.2.6 - autoclosed Update dependency vite to v5.2.6 Mar 29, 2024
@renovate renovate bot reopened this Mar 29, 2024
@renovate renovate bot restored the renovate/vite-5.x-lockfile branch March 29, 2024 09:03
@renovate renovate bot force-pushed the renovate/vite-5.x-lockfile branch from fc207ff to 5a9d152 Compare March 29, 2024 09:04
@renovate renovate bot changed the title Update dependency vite to v5.2.6 Update dependency vite to v5.2.7 Mar 29, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.7 Update dependency vite to v5.2.8 Apr 3, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.8 Update dependency vite to v5.2.9 Apr 16, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.9 Update dependency vite to v5.2.10 Apr 20, 2024
@renovate renovate bot changed the title Update dependency vite to v5.2.10 Update dependency vite to v5.2.10 - autoclosed Apr 24, 2024
@renovate renovate bot closed this Apr 24, 2024
@renovate renovate bot deleted the renovate/vite-5.x-lockfile branch April 24, 2024 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants