Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@
"prepare": "husky"
},
"dependencies": {
"@rc-component/context": "^1.4.0",
"@rc-component/context": "^2.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

Upgrading @rc-component/context to a new major version (from v1.x to v2.x) likely introduces breaking changes. This pull request only updates the dependency version in package.json but lacks the necessary code changes to adapt to the new version's API. This can lead to build failures or runtime errors. Please include the required code modifications for compatibility with v2 or consider reverting this change if the project is not ready for the upgrade.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

版本升级会导致安装失败
截至 2025 年 9 月 29 日,npm 上 @rc-component/context 的最新可用版本仍是 1.4.0(发布于 2 年前),尚不存在 2.0.0。直接将依赖提升到 ^2.0.0 会让安装过程在解析版本时失败,请先确认上游已经发布对应版本或调整到实际存在的版本号。(npmjs.com)

🤖 Prompt for AI Agents
In package.json around line 52, the dependency was changed to
"@rc-component/context": "^2.0.0" but that version does not exist on npm and
will break installs; revert or pin to a published version (for example "^1.4.0"
or the exact "1.4.0") or confirm upstream has released 2.0.0 before using it,
then update package.json accordingly and regenerate the lockfile (npm install /
yarn install) to ensure consistent dependency resolution.

"@rc-component/resize-observer": "^1.0.0",
"@rc-component/util": "^1.1.0",
"clsx": "^2.1.1",
Expand Down
Loading