Upgraded Mux Player to 3.8.0 to fix issues with native chrome #441
+278
−92
Conversation
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
|
@spuppo-mux is attempting to deploy a commit to the Sanity Sandbox Team on Vercel. A member of the Team first needs to authorize it. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
sjelfull
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Closes #440
Upgraded the dependency for Mux Player to v3.8.0 to fix an issue that came up with recent Chrome 142 update.
What to review
All references to the Mux player dependency have been upgraded.
Testing
To test this I first upgraded Chrome to verify I could reproduce the issue. In particular, I used the default Movie asset in Mux Dashboard.
Then, after upgrading the dependency, I could confirm that this error no longer happens.
I also did some smoke testing by using different player features to ensure nothing new was broken. Did the same for Safari.