Repository navigation
Update dependency react-intl to v10.1.25 - autoclosed #226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,7 +25,7 @@ | |
| "@tanstack/react-query": "5.101.4", | ||
| "react": "19.2.8", | ||
| "react-dom": "19.2.8", | ||
| "react-intl": "10.1.18", | ||
| "react-intl": "10.1.25", | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [Major] Same inconsistency as the gateway package: |
||
| "victory-area": "37.3.6", | ||
| "victory-core": "37.3.6", | ||
| "victory-group": "37.3.6", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Major] react-intl is bumped to
10.1.25here inpeerDependencies, but this same file still pinsreact-intl: 10.1.18indevDependencies(L57), andpnpm-lock.yamlstill resolves10.1.18. The package therefore declares a peer requirement of10.1.25while continuing to build and test against10.1.18. Bump both entries and regenerate the lockfile so the declared peer, the installed dev version, and the lockfile all agree.