Unverified50% confidenceSolutionExact time
The more prudent way to use @cline/core is to hard-code an exact version (such as 0.0.93) in package.json rather than using a range notation like ^0.0.93.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/13/2026
First Seen
Valid until: 1/11/2027
Sources
Related Entities
Related Claims
UnverifiedFor @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 issues79% similarUnverifiedUsing semantic version range locking in package.json (e.g., ^3.0.0 rather than an exact version) can maintain flexibility while reducing the risk of accidentally introducing breaking changes.66% similarVerifiedUsing the range specifier ^1.0.0 in package.json will automatically accept all MINOR and PATCH updates under the same MAJOR version64% 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 risks63% similarUnverifiedFor package.json files that depend on 0.0.x versions, it is not recommended to use loose version ranges such as ^ or ~; instead, exact version numbers should be used to avoid pulling in incompatible updates.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016296API
curl https://kongchang.com/api/v1/knowledge/claims/1016296MCP
get_claim(id=1016296)