build(deps-dev): upgrade Jest from v29 to v30.2.0#1912
Merged
madhavilosetty-intel merged 1 commit intomainfrom Feb 27, 2026
Merged
build(deps-dev): upgrade Jest from v29 to v30.2.0#1912madhavilosetty-intel merged 1 commit intomainfrom
madhavilosetty-intel merged 1 commit intomainfrom
Conversation
151cccb to
3810e48
Compare
Upgrade jest, jest-environment-jsdom, jest-util to 30.2.0 and @types/jest to 30.0.0. Update test assertions to use computed RGB color values as the newer jsdom resolves named CSS colors to RGB.
3810e48 to
dd3d22e
Compare
graikhel-intel
approved these changes
Feb 27, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrade jest, jest-environment-jsdom, jest-util to 30.2.0 and @types/jest to 30.0.0. Update test assertions to use computed RGB color values as the newer jsdom resolves named CSS colors to RGB.
PR Checklist
What are you changing?
Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )