Repository navigation
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
4 tasks done
Contributor
Author
|
Proof done: the peer check failed on React 19, https://github.com/datum-cloud/datum.net-cms/actions/runs/40731799140 |
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.
Throwaway proof for #33. Closes without merging.