fix: storage package dependency versions

[designcode]

Note

Locks @tigrisdata/storage to ^2.0.0 in packages/keyv-tigris and packages/react to avoid floating versions.

• Updates package-lock.json to resolve @tigrisdata/storage to 2.12.0 with new AWS/Smithy transitive deps
• No application code changes; only dependency constraints and lockfile updates

^{Written by Cursor Bugbot for commit aeebd58. This will update automatically on new commits. Configure here.}

[greptile-apps]

Greptile Overview

Greptile Summary

Changes @tigrisdata/storage dependency from wildcard (*) to ^2.0.0 in packages/keyv-tigris and packages/react, resolving to version 2.12.0 from npm registry.

• Critical Issue: This breaks workspace resolution in the monorepo. The packages will now use the published npm version (2.12.0) instead of the local workspace version (0.0.1)
• Local changes to @tigrisdata/storage won't be reflected in dependent packages during development
• The package-lock.json shows packages/keyv-tigris/node_modules/@tigrisdata/storage and packages/react/node_modules/@tigrisdata/storage now resolve to npm registry instead of workspace link
• Adds 270 lines of AWS/Smithy transitive dependencies to lockfile

For a monorepo setup with workspace packages, dependencies should typically use workspace:* or remain as * to use local versions during development.

Confidence Score: 1/5

• This PR breaks the monorepo workspace resolution and will cause issues during local development
• The change from wildcard to ^2.0.0 forces npm to resolve from registry instead of workspace, breaking the fundamental monorepo pattern where packages should depend on local workspace versions during development
• Both packages/keyv-tigris/package.json and packages/react/package.json need attention - the dependency declarations should use workspace:* to preserve workspace resolution

Important Files Changed

Filename	Overview
packages/keyv-tigris/package.json	Changed @tigrisdata/storage from wildcard (*) to ^2.0.0, locks to published npm package instead of workspace
packages/react/package.json	Changed @tigrisdata/storage from wildcard (*) to ^2.0.0, locks to published npm package instead of workspace
package-lock.json	Resolves @tigrisdata/storage to 2.12.0 from npm with new AWS/Smithy dependencies in workspace node_modules

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

changing from * to ^2.0.0 breaks workspace resolution - packages/keyv-tigris will now use the published npm package (2.12.0) instead of the local workspace version (0.0.1), which breaks local development workflow

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/keyv-tigris/package.json
Line: 48:48

Comment:
changing from `*` to `^2.0.0` breaks workspace resolution - `packages/keyv-tigris` will now use the published npm package (2.12.0) instead of the local workspace version (0.0.1), which breaks local development workflow

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

changing from * to ^2.0.0 breaks workspace resolution - packages/react will now use the published npm package (2.12.0) instead of the local workspace version (0.0.1), which breaks local development workflow

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/react/package.json
Line: 58:58

Comment:
changing from `*` to `^2.0.0` breaks workspace resolution - `packages/react` will now use the published npm package (2.12.0) instead of the local workspace version (0.0.1), which breaks local development workflow

How can I resolve this? If you propose a fix, please make it concise.

[github-actions]

🎉 This PR is included in version 1.1.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.2.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀