Unverified50% confidenceFactExact time
A dependency-sync patch means the package's own source code is unchanged and the version number increase is triggered only by a raised dependency version range in package.json
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAdapter packages usually depend on the core package with exact versions or very narrow ranges in package.json, so when ai releases a new patch, the adapter packages often also release patch versions accordingly to keep versions aligned.73% similarUnverifiedUsing a caret constraint such as ^1.0.130 in package.json allows automatically receiving subsequent patch updates while blocking minor version upgrades that may introduce incompatibility risks71% similarUnverifiedUsing the version range ^2.0.x in package.json allows you to benefit from patch fix improvements while avoiding breaking changes in major versions.71% similarUnverifiedFor @cline/shared in the 0.0.x stage, it is recommended to use exact version numbers in package.json rather than ^ or ~ range specifiers to prevent automatic upgrades from triggering compatibility issues71% similarUnverifiedUsing ^3.0.276 in package.json means accepting all updates within the same MAJOR version, while ~3.0.276 only accepts PATCH-level updates.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1039720API
curl https://kongchang.com/api/v1/knowledge/claims/1039720MCP
get_claim(id=1039720)