fix(cli): update @anthropic-ai/sdk constraint from ^0.32.0 to ^0.92.0#248
Open
fix(cli): update @anthropic-ai/sdk constraint from ^0.32.0 to ^0.92.0#248
Conversation
The package.json had ^0.32.0 but the lock file contained 0.92.0. On a fresh npm install, npm would resolve ^0.32.0 to 0.32.1 (the latest patch in that range), installing a version ~60 releases behind what the codebase was developed and tested against. This mismatch would silently break API calls on new installs. Align the constraint with what is actually installed and tested.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Update the
@anthropic-ai/sdkversion constraint inCLI/package.jsonfrom^0.32.0to^0.92.0.Why
The package.json declared
^0.32.0, but the lock file (and installed version) was0.92.0. These two were out of sync in a way that silently breaks new installs:^0.32.0resolves to>=0.32.0 <0.33.0under semver — so a freshnpm installwould pull in0.32.1, a version ~60 releases behind0.92.0, meaning new contributors would get unexpected behaviour or broken API callsnpm outdatedsurfaced this clearly:Tested
npm test)