@uniswap/v2-sdk@4.19.2 published with workspace:* dependency, breaks all consumers

[rin-st]

@uniswap/v2-sdk@4.19.2 has @uniswap/sdk-core: "workspace:*" in its dependencies — a monorepo-internal reference that was accidentally published to npm.

This breaks npm/yarn/pnpm install for any project that depends on @uniswap/v2-sdk@^4.x:

Error: @uniswap/sdk-core@workspace:*: Workspace not found

4.19.1 is fine (@uniswap/sdk-core: "^7.12.1"). Only 4.19.2 is affected.

Expected: workspace:* should be resolved to a proper semver range before publishing.

[rodiazet]

The same problem for v3-sdk:

npm --version && npm i @uniswap/v3-sdk

11.9.0
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "workspace:": workspace:*
npm error A complete log of this run can be found in: /Users/rodia/.npm/_logs/2026-03-13T11_44_27_515Z-debug-0.log

[Genmin]

I re-checked the current published packages from npm and this appears fixed for the latest v2/v3 releases.

Verification:

• npm view @uniswap/v2-sdk@latest version dependencies --json reports 4.20.0 with @uniswap/sdk-core: ^7.13.0
• npm view @uniswap/v3-sdk@latest version dependencies --json reports 3.30.0 with @uniswap/sdk-core: ^7.13.0
• A clean npm install @uniswap/v2-sdk@^4 @uniswap/v3-sdk@^3 --package-lock-only --ignore-scripts resolves v2 4.20.0 and v3 3.30.0 without the workspace:* protocol error

It looks like #562 added the release-side workspace protocol resolver that prevents newly published packages from leaking monorepo-internal workspace:* ranges. The broken 4.19.2 / affected v3 publish will still remain broken if consumers pin that exact version, but ^4 / ^3 consumers should now move to the fixed latest versions.