Skip to content

chore(deps): update dependency vite to v7.2.10 (main)#39891

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/main-vite-7.x
Dec 10, 2025
Merged

chore(deps): update dependency vite to v7.2.10 (main)#39891
renovate[bot] merged 1 commit intomainfrom
renovate/main-vite-7.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 10, 2025

This PR contains the following updates:

Package Change Age Confidence
vite (source) 7.2.9 -> 7.2.10 age confidence

Release Notes

vitejs/rolldown-vite (vite)

v7.2.10

Compare Source

Features
Bug Fixes
Documentation
Tests

Configuration

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

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

| datasource | package       | from  | to     |
| ---------- | ------------- | ----- | ------ |
| npm        | rolldown-vite | 7.2.9 | 7.2.10 |
@renovate renovate Bot enabled auto-merge December 10, 2025 08:27
@renovate renovate Bot added this pull request to the merge queue Dec 10, 2025
Merged via the queue into main with commit 58f748f Dec 10, 2025
42 checks passed
@renovate renovate Bot deleted the renovate/main-vite-7.x branch December 10, 2025 08:38
jamietanna added a commit that referenced this pull request Dec 12, 2025
Since the upgrade yesterday in #39891, we've seen a bit more flakiness
in our CI pipeline, as noted in #39921.

Although we've not confirmed if this is the issue, it appears to be
suspicious timing.

Out of an abundance of caution, we'll revert the upgrade to see if this
resolves the issue.

This reverts commit 58f748f.
github-merge-queue Bot pushed a commit that referenced this pull request Dec 12, 2025
Since the upgrade yesterday in #39891, we've seen a bit more flakiness
in our CI pipeline, as noted in #39921.

Although we've not confirmed if this is the issue, it appears to be
suspicious timing.

Out of an abundance of caution, we'll revert the upgrade to see if this
resolves the issue.

This reverts commit 58f748f.
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jan 10, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants