fix(deps): port yellowstone-grpc ESM type-marker patch to 5.0.9

[rz1989s]

What

Ports the @triton-one/yellowstone-grpc ESM type-marker patch from 4.0.2 to 5.0.9, unblocking the minor-and-patch group PR (#376), whose @sip-protocol/sdk 0.11.0 → 0.15.1 bump requires @triton-one/yellowstone-grpc ^5.0.9.

The 5.0.9 tarball (like 4.0.2) ships dist/esm/ without type markers: the root package.json has no type field, so Node/tsx treat the ESM build as CJS and the sdk's static re-export of yellowstone fails to named-ESM-import. A plain regen of #376 fails ERR_PNPM_PATCH_NOT_APPLIED; Dependabot's own regen also drops the patchedDependencies section entirely — hence this hand-ported patch PR.

Patch content (5.0.9)

File	Marker	Why
dist/esm/package.json	{"type":"module"}	marks the ESM build (same as the 4.0.2 patch)
dist/esm/napi/package.json	{"type":"commonjs"}	new, 5.0.9-specific: NAPI-RS generates CJS content (module.exports = nativeBinding, 83 require() calls) inside the esm tree; a blanket type:module would break it. ESM import * as napi still resolves GrpcClient and the other named exports via CJS interop

4.0.2 hunk dropped, entry replaced (not kept): 5.0.9 removed the wasm dist/esm/encoding/ directory, so the 4.0.2 patch's dist/esm/encoding/package.json hunk has no target. pnpm 10 hard-errors on unused patch declarations (ERR_PNPM_UNUSED_PATCH — verified in both directions: a 5.0.9 declaration with sdk at 0.11.0 errors, a 4.0.2 declaration with sdk at 0.15.1 errors), and nothing else in the workspace resolves 4.0.2 (yellowstone is reachable only via @sip-protocol/sdk), so exact-version patch keys force a cutover.

@sip-protocol/sdk ^0.11.0 → ^0.15.1 included (root, packages/sdk, examples/vault-privacy-provider): the minimal change that puts yellowstone 5.0.9 in the graph, making the patch declaration valid. The other 33 bumps of the #376 group are untouched and remain with #376.

pnpm-lock.yaml is an honest full regen on current main base (c67e707) with pnpm 10 (matching CI's version: 10).

Evidence (three proofs)

1. Frozen install + suite on this branch (pnpm 10, matching CI):

• pnpm install --frozen-lockfile green
• pnpm typecheck green
• pnpm test -- --run → 563/563 tests, 36 files green

2. Patch behavior, before/after on 5.0.9:

• Pristine 5.0.9 dist/esm/index.js: Node emits MODULE_TYPELESS_PACKAGE_JSON ("doesn't parse as CommonJS … add type: module") — Node itself prescribes the patch's fix
• Patched 5.0.9: named-ESM import succeeds with 42 top-level exports; napi CJS-in-esm interop resolves GrpcClient: function, AUTORECONNECT_FILTER_KEY: string

3. Post-#376 regen sim (throwaway branch off this state, not pushed): applied all 42 version deltas from #376's five package.json files, honest pnpm install --no-frozen-lockfile regen → --frozen-lockfile green (idempotent), typecheck green, suite 563/563.

After this merges, for #376

@dependabot rebase on #376 (its current branch carries a mangled lockfile that dropped patchedDependencies, so a regen is required either way) → CI gate → merge. With the sdk bump already on main, dependabot's regenerated diff shrinks to the remaining group bumps.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sipher	Ready	Preview	Sep 23, 2026 11:27pm UTC