chore(deps): downgrade vite to v7.2.9#39930
Merged
jamietanna merged 1 commit intomainfrom Dec 12, 2025
Merged
Conversation
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.
Contributor
Author
|
I'm going to run CI several times on this branch to get some more data about whether it does fix this |
viceice
approved these changes
Dec 12, 2025
Contributor
Author
|
3 runs so far have been all green, 4th pending then will merge |
Contributor
|
🎉 This PR is included in version 42.50.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
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 #39891.
Context
Please select one of the below:
AI assistance disclosure
Did you use AI tools to create any part of this pull request?
Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
The public repository: