Skip to content

chore: Upgrade react, react-router and react-router-dom - #240

Draft
jperals wants to merge 1 commit into
mainfrom
chore/upgrade-react-router-dom
Draft

chore: Upgrade react, react-router and react-router-dom#240
jperals wants to merge 1 commit into
mainfrom
chore/upgrade-react-router-dom

Conversation

@jperals

Copy link
Copy Markdown
Member

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

amanabiy added a commit that referenced this pull request Aug 21, 2026
Add overrides: { '@puppeteer/browsers': '^3.2.0' } to force
@wdio/utils off @puppeteer/browsers 2.x (which requires extract-zip
2.0.1). @puppeteer/browsers 3.x replaced extract-zip with modern-tar.
No patched version of extract-zip exists (first_patched_version: null),
so elimination via @puppeteer/browsers upgrade is the only available
fix. Rung 4 (overrides) — rung 1/2/3 cannot resolve a package with no
patched release. This pattern is precedented across this org.
The react-router alerts (#197, #198, #199) are NOT addressed here
because react-router-dom 7.x requires react@>=18 while this repo uses
react@^16.14.0. Bumping both is a breaking change handled separately
by the open PR #240.
Alert addressed:
- GHSA-jmr9-qjv8-65gv / CVE-2026-56876 (extract-zip <= 2.0.1, high)
extract-zip: 2.0.1 -> eliminated from tree
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@jperals