Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@sei-js/precompiles@3.1.0

Minor Changes

• b7f4e54: Add getLogsInRange, streamLogsInRange, blockRanges and MAX_GET_LOGS_BLOCK_RANGE for reading logs across a block range.

  eth_getLogs is capped per request, so reading more history than one request allows means walking it in chunks, and every project that needs logs writes that loop again. This walk only sends requests a Sei node can answer. Spans are counted inclusively the way the node counts them (2000 blocks passes, 2001 is refused). A span too heavy to answer is halved and asked again, whether the node refuses it for matching more than max_log_no_block logs (sei-chain v6.7 and later), the response passes viem's size limit (before v6.7, when bounded requests are served whole), or the span times out. A node whose refusal names a smaller max_blocks_for_log is walked at that, and busy or rate limited refusals are retried with backoff. Every request carries an explicit toBlock, because nodes before v6.7 silently cut an open-ended request off at the log cap.

  streamLogsInRange yields each chunk with its logs, so a backfill can store as it goes and resume from the last toBlock. getLogsInRange collects the walk into one array and awaits an optional onChunk for each chunk. Both take viem's getLogs filter (address, event with args, events, strict), accept a whole contract ABI as events, and take any viem Client, including one that carries an account. Without a toBlock they read to the head, since Sei finalises a block as it is produced. blockRanges gives the fixed-width plan without making requests.

  No dependency or peer range changes: this uses the viem peer already declared.

@sei-js/create-sei@2.0.1

Patch Changes

• cb882eb: Bump the Next template's next and sharp pins to clear three newly published advisories.

  The generated-app smoke audits every variant and fails on any high or critical finding. Three advisories landed against the pinned versions, so the check went red without any change to the template:

  • GHSA-p293-qw3h-jr36 — critical, unauthenticated RCE on Windows-hosted Next.js servers, >=13.4.0 <15.5.24.
  • GHSA-2xp9-vwfh-vxw4 — critical, unauthenticated RCE in the Image Optimization API when AVIF files are used, >=10.0.0 <15.5.24.
  • GHSA-rgj7-g3m4-5g8c — high, heap overflow in Sharp's bundled libheif decoder, <0.35.4.

  next moves 15.5.21 to 15.5.25 and the sharp override 0.35.3 to 0.35.4, both inside their pinned minors.

  Next also widened its own Sharp declaration to ^0.34.3 || ^0.35.4, so the pinned override now sits inside the range Next supports. The image notes in the template README and next.config.mjs said the opposite and are corrected: images stay unoptimized to avoid requiring a native Sharp build, which is a template choice rather than a security tradeoff. The sharp override itself still is one, and both notes now say so — the 0.34.x half of Next's range remains inside the advisory, making 0.35.4 the floor rather than a free upgrade.

  The remaining decode-uri-component finding is moderate and does not block the smoke.

@sei-js/mcp-server@1.0.1

Patch Changes

• 5a40dc8: Keep each MCP runtime on the wallet configuration that passed its security check.

  A later programmatic main() could overwrite the process-wide config object while an HTTP listener started earlier was still serving requests. New sessions on that listener then built their tool list from the updated singleton, so a wallet-disabled HTTP server could expose signing tools after a trusted stdio start in the same process. No shipped CLI or host spawn does that, but the public lifecycle returned independent runtimes without isolating their keys.

  parseArgs() now returns a frozen AppConfig snapshot, and every transport handles requests against that snapshot. Stopping one runtime evicts only its provider cache entry, while other runtimes keep their original signer. HTTP transports require that snapshot and derive signing policy from it.

@sei-js/sei-global-wallet@2.0.1

Patch Changes

• 66deb15: Document that @dynamic-labs/ethereum-aa has to match the @dynamic-labs/global-wallet-client version npm resolves, and keep the release checks on that resolved version instead of a constant.

  Dynamic declares @dynamic-labs/ethereum-aa as an exact peer of its client and pins its internal packages to the client's version, so the two move together on every patch. @dynamic-labs/global-wallet-client is a ^4.96.3 dependency here, which means a Dynamic patch inside that range changes the peer version consumers need. Pinning an older @dynamic-labs/ethereum-aa than the resolved client does not fail the install: npm cannot place the client's exact peer beside the older root copy, so it nests the client under this package and duplicates the whole Dynamic runtime. The Optional peer versions table now states this and shows how to read the version the resolved client asks for.

  The consumer verifier resolved 4.96.3 regardless of what the range resolved to, so Dynamic publishing @dynamic-labs/global-wallet-client@4.96.4 turned the nightly consumer run red on a duplicated Dynamic subtree rather than on any change in this repository. It now resolves the declared range against the registry, pins that client and the peer version it requests in each full consumer, and reports both, so a Dynamic patch is exercised the way an application receives it while a peer pin moving outside this package's published range still fails. A client that npm nests instead of hoisting is now reported as such, rather than as an unresolved dependency.

  No published dependency or peer range changes.

• cb882eb: Override the newly advised sharp pin, and waive the one optional-AA advisory that no override can reach.

  Two advisories published against the existing dependency graph, so the nightly consumer run went red without any change in this repository.

  GHSA-rgj7-g3m4-5g8c covers sharp below 0.35.4, and @dynamic-labs/iconic pins sharp@0.35.0 exactly. That is the same shape as the existing Axios and UUID pins: the vulnerable copy is reachable from @dynamic-labs/global-wallet-client, overrides are root-only in both npm and Bun, and this package cannot propagate them to an application. A plain install reported nine high findings, one root advisory cascading up the Dynamic chain to @sei-js/sei-global-wallet itself. The Required consumer overrides blocks now carry "sharp": "0.35.4", a patch-level move inside the pinned minor. The advisory is a heap overflow in the bundled libheif decoder, so it needs untrusted HEIF input to trigger and sharp is a build-time dependency of the icon package that never reaches a browser bundle, but it is high severity with a compatible fix available, so it is corrected rather than waived.

  GHSA-528h-pc64-c93x covers every stream-json up to 3.4.0, which the Solana RPC client's jayson requires as CommonJS on the optional AA path. It cannot be overridden: 3.5.0 onward is ESM-only under a moved src/ layout, so pointing jayson at a fixed version replaces the advisory with a MODULE_NOT_FOUND on its own require, and every CommonJS version is inside the advisory. It is now an accepted advisory for the full npm consumer, alongside the Bun waiver that already existed for advisories with no compatible fix. The finding is an O(depth²) slowdown in filters that no wallet path feeds, and the wallet-only npm consumer is still held to a strictly clean audit with no waiver, so a default install is unaffected.

  Several verifier gaps this exposed are closed as well.

  The npm audits ran without allowing a non-zero exit, so any finding surfaced as a raw spawn error carrying the whole audit JSON rather than the assertion naming the consumer; they now fail with the offending package and advisory URL. Allowing that exit means the body has to be validated, because npm audit fails the same way when it cannot reach the registry: an ENOAUDIT payload carries no counts, so an unvalidated report would read as zero findings and turn an audit that never ran into a pass on the gate this check exists to enforce. Every npm audit result is now rejected unless it carries a real vulnerability count.

  The "overrides still required" report and the Bun "overrides are taking effect" assertion are now derived from the override block instead of a hardcoded axios/uuid list, so a newly overridden package cannot be left out and let a partial upstream fix ask for the whole waiver to be dropped. The README override blocks are asserted against the sets the consumers install, so the three hand-maintained copies cannot document an override that is never tested.

  The audit and override-parsing helpers moved into scripts/consumer-audit.ts and scripts/documented-overrides.ts with unit tests, so these cases are pinned by bun test --isolate scripts rather than only by a full consumer run.

  No published dependency or peer range changes.

[cursor]

PR Summary

Medium Risk
The release includes MCP wallet-config isolation (security fix) and precompiles log-range RPC behavior; create-sei and sei-global-wallet changes are mostly advisory/docs/CI with documented consumer overrides.

Overview
Changesets release that bumps four @sei-js packages on npm and records their release notes; consumed .changeset files are removed and bun.lock workspace versions are updated.

@sei-js/precompiles@3.1.0 (minor) ships chunked eth_getLogs helpers: getLogsInRange, streamLogsInRange, blockRanges, and MAX_GET_LOGS_BLOCK_RANGE, with Sei-aware span splitting, retries, and explicit toBlock handling.

@sei-js/create-sei@2.0.1 bumps the Next.js template pins (next 15.5.25, sharp 0.35.4) to clear critical/high advisories and corrects template docs about unoptimized images vs the sharp override.

@sei-js/mcp-server@1.0.1 isolates wallet policy per runtime by using a frozen AppConfig snapshot from parseArgs() so concurrent HTTP and stdio lifecycles cannot leak signing tools across configs.

@sei-js/sei-global-wallet@2.0.1 documents Dynamic @dynamic-labs/ethereum-aa peer alignment, tightens consumer verification (registry-resolved client version, audit validation, override lists derived from README blocks, sharp 0.35.4 in required overrides), and waives the unfixable optional-AA stream-json advisory. No published dependency range changes in this release metadata.

^{Reviewed by Cursor Bugbot for commit f56e0c1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[seidroid]

The automated review did not complete; see the failing AI Review check for details.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.17%. Comparing base (66deb15) to head (01bff01).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #348   +/-   ##
=======================================
  Coverage   97.17%   97.17%           
=======================================
  Files          80       80           
  Lines        5410     5410           
=======================================
  Hits         5257     5257           
  Misses        153      153           

Flag	Coverage Δ
mcp-server	96.13% <ø> (ø)
precompiles	100.00% <ø> (ø)
registry	100.00% <ø> (ø)
sei-global-wallet	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.