Repository navigation
chore: bump deps - #899
Merged
Merged
chore: bump deps#899
Conversation
lukasmatta
requested review from
TerranceKhumalo-absa,
fateeand and
korel-san
as code owners
October 28, 2026 22:39
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
Contributor
Coverage report for library
Test suite run success3257 tests passing in 76 suites. Report generated by 🧪jest coverage report action from 944893d |
Contributor
Playwright test results
Details
|
fateeand
approved these changes
Oct 29, 2026
This was referenced Oct 29, 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.
Bump dependencies to resolve dependabot tickets.
Temporarily disabled
label-content-name-mismatch, newly enabled by default in axe-core4.14.0, because it exposes existing WCAG 2.5.3 label-in-name issues across several components. Opened a follow up ticket for this - #900.