Repository navigation
ci: Fail on React and router versions Strapi rejects - #37
Conversation
The admin build only warns on a React 19 or react-router-dom 7 bump, and .npmrc sets legacy-peer-deps so install accepts them, so CI passed upgrades Strapi 5.59 cannot run. Key features/changes: - Run npm ls on react, react-dom, react-router-dom and styled-components, which exits non-zero on a version outside Strapi's peer ranges - Hold react and react-dom below 19 and react-router-dom below 7 in Renovate until Strapi raises its ranges
|
Warning Polylane could not verify the production impact of this pull request. I checked the resulting Also considered · 3 refuted
Analysed against 1 cloud account and 1 repository
Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to. Polylane analysed Rate this review: 👍 helpful · 👎 not helpful · 😕 confusing |
A React 19 or react-router-dom 7 upgrade to the blog CMS passes CI today and breaks the admin panel Strapi 5.59 serves. This adds a CI step that fails on any React, router or styled-components version outside Strapi's declared peer ranges, and a Renovate rule that stops opening React 19 and router 7 upgrades until Strapi supports them.
Related to #33
Test plan
renovate-config-validatoraccepts the new config