-
Notifications
You must be signed in to change notification settings - Fork 2.7k
chore(deps): update dependency @types/react to v18.3.27 #7763
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
base: main
Are you sure you want to change the base?
Conversation
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.
Thank you for this dependency update! However, I found an issue that needs to be addressed: the package.json files haven't been updated to match the lockfile changes.
| @@ -241,10 +241,10 @@ importers: | |||
| version: 1.1.6 | |||
| '@types/react': | |||
| specifier: ^18.3.23 | |||
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.
The lockfile has been updated to use @types/react version 18.3.24, but the package.json files in the following locations still reference version ^18.3.23:
- apps/web-evals/package.json (line 55)
- webview-ui/package.json (line 91)
- apps/web-roo-code/package.json (line 43)
Could you please update these package.json files to specify "@types/react": "^18.3.24" to maintain consistency between the package manifests and the lockfile? This inconsistency could lead to version conflicts and unexpected behavior.
a02fd83 to
e895bb1
Compare
e1e81d6 to
5ee444b
Compare
697b0f0 to
f9d24d5
Compare
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.
No new issues found - all concerns already addressed in existing comments.
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.
No new issues found - all concerns already addressed in existing comments.
f9d24d5 to
7333e8c
Compare
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.
I found some issues that need attention. See inline comment(s).
| @@ -241,10 +241,10 @@ importers: | |||
| version: 1.1.6 | |||
| '@types/react': | |||
| specifier: ^18.3.23 | |||
| version: 18.3.23 | |||
| version: 18.3.26 | |||
| '@types/react-dom': | |||
| specifier: ^18.3.5 | |||
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.
[P2] Inconsistent @types/react-dom specifiers across workspaces. The lockfile resolves to 18.3.7, but package.json manifests specify different ranges: apps/web-evals and webview-ui use ^18.3.5 while apps/web-roo-code uses ^18.3.7. Recommend aligning all manifests to ^18.3.7 (or a single ^18.3.x) to avoid drift and ensure consistent installs: - apps/web-evals/package.json line 56 -> "@types/react-dom": "^18.3.7" - webview-ui/package.json line 94 -> "@types/react-dom": "^18.3.7" - apps/web-roo-code/package.json line 46 is already ^18.3.7.
7333e8c to
7fb0982
Compare
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.
No new issues found - all concerns already addressed in existing comments.
7fb0982 to
bab7d4c
Compare
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.
No new issues found - all concerns already addressed in existing comments.
bab7d4c to
110941d
Compare
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.
The previous review incorrectly identified an issue with package.json files not being updated. This is actually correct behavior: the package.json files specify ^18.3.23 for @types/react, which means 'compatible with 18.3.23'. The lockfile correctly resolves this to 18.3.26, which is a valid patch update within the semver range. No package.json changes are needed for this type of dependency update.
110941d to
8ac5a34
Compare
Review CompleteThis PR correctly updates No new actionable issues were found in this update. The 3 previously flagged issues remain valid but are minor version management suggestions that don't affect functionality:
Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues. |
ee66584 to
cc7e0c2
Compare
cc7e0c2 to
dd3f96a
Compare
dd3f96a to
34744c7
Compare
34744c7 to
55faa2f
Compare
55faa2f to
b1fe767
Compare
b1fe767 to
c317048
Compare
c317048 to
166091e
Compare
This PR contains the following updates:
18.3.23β18.3.27Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.