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

nansen-cli@2.1.0

Minor Changes

• #728 c5ef96f Thanks @gulshngill! - Drop support for Node.js 20 (EOL since April 2026). The minimum supported version is now Node.js 22: engines.node is >=22.0.0, CI tests on Node 22 and 24, and nansen doctor reports Node 20 as below the required version.

• #584 435ae1a Thanks @ygd58! - nansen wallet list now prints the standard JSON envelope on stdout, {"success":true,"data":{"wallets":[...],"defaultWallet":...}}, so nansen wallet list | jq . works and --pretty, --table, --format csv and --fields apply to it like any other command. It previously printed a readable summary with no data envelope, which agents could not parse. The output is the same in a terminal and in a pipe; use --pretty for readable JSON or --table for a table. With no wallets it returns an empty wallets list instead of a hint.

• #727 9404c13 Thanks @hulk-linus! - nansen wallet show <name> now prints the standard JSON envelope on stdout, {"success":true,"data":{"name":...,"provider":...,"evm":...,"solana":...,"createdAt":...,"isDefault":...}}, so nansen wallet show main | jq . works and --pretty, --table, --format csv and --fields apply to it. Privy wallets also include privyWalletIds. The redacted default of nansen wallet export <name> does the same, returning {"name":...,"redacted":true,"evm":{"address":...},"solana":{"address":...}} with no key fields. Both previously printed a readable summary that agents could not parse. wallet export --reveal and --file are unchanged.

Patch Changes

• #724 1f2fc6e Thanks @hulk-linus! - Use the resolved gas limit when signing local EVM swaps, including quotes with both gas and gasLimit fields.

• #731 f4cf188 Thanks @hulk-linus! - Reject symlinks, hard links, and replaced files when reading saved authentication and trading quotes. Validate authentication lock descriptors before use. Claim bridge quotes before signing and block reuse if a post-broadcast execution marker cannot be saved. Authentication reads now require user-owned paths without group or other write permissions on POSIX; repair permissions before retrying an unsafe saved-key read.

• #729 7b54c0e Thanks @gulshngill! - Solana-source bridge routes that are too large to fit in a transaction without address lookup tables (for example a token swap ahead of the bridge deposit) now compile and sign. The CLI fetches the route's lookup tables, checks that each one is active and on-chain, and uses them to compress accounts. Routes that already fit are compiled as before.

• #733 353629a Thanks @kome12! - trade execute: accept a capitalised chain name. trade quote --chain Base stores the chain exactly as you typed it, but the RPC registry is keyed lowercase, so the quote could be created and then never executed ("No RPC URL configured for chain: Base"). The chain is now normalised once when the quote is loaded, which also fixes quotes already on disk.

[nansen-pr-reviewer]

pr-reviewer Summary for #2304473

✅ No issues found

The code review completed successfully with no findings.

Review effort: 1/5 (Trivial)

Summary

This is an auto-generated Changesets release PR bumping nansen-cli from 2.0.1 → 2.1.0. The diff touches only package.json, package-lock.json, CHANGELOG.md, and the deletion of three consumed .changeset/*.md files — no production code is changed.

The semver level is correct: two minor-tagged changesets (wallet list JSON envelope output and wallet show / redacted wallet export JSON envelope output) and one patch (resolved gas limit for EVM swaps) correctly combine to a minor bump. The package name "nansen-cli" matches in all three changeset files and in package.json. CHANGELOG entry content matches the PR description. Nothing is structurally wrong with this release.

Safe to merge whenever the team is ready to publish.

---

Token usage: 71 input, 1,371 output, 96,859 cache read, 25,720 cache write | Usage Guide

New pushes are reviewed automatically with a 10-minute cooldown between reviews. To request a review at any time, comment @nansen-pr-reviewer re-review.

[nansen-pr-reviewer]

Auto-approved

This PR was automatically approved because:

• Claude recommends approval
• Claude assessed this as a minimal effort change
• The effort level is within the auto-approval threshold of 2
• No high or critical issues were detected

If you have any concerns, please request a manual review.

[nansen-pr-reviewer]

Auto-approved

This PR was automatically approved because:

• Claude recommends approval
• Claude assessed this as a minimal effort change
• The effort level is within the auto-approval threshold of 2
• No high or critical issues were detected

If you have any concerns, please request a manual review.

[nansen-pr-reviewer]

Auto-approved

This PR was automatically approved because:

• Claude recommends approval
• Claude assessed this as a minimal effort change
• The effort level is within the auto-approval threshold of 2
• No high or critical issues were detected

If you have any concerns, please request a manual review.

[nansen-pr-reviewer]

Auto-approved

This PR was automatically approved because:

• Claude recommends approval
• Claude assessed this as a minimal effort change
• The effort level is within the auto-approval threshold of 2
• No high or critical issues were detected

If you have any concerns, please request a manual review.

[nansen-pr-reviewer]

nansen-pr-reviewer summary

This is a standard Changesets release commit: it publishes version 2.1.0, records the pending changesets in CHANGELOG.md, updates package metadata and lockfile versions, and removes the consumed changeset files. No correctness, security, or dependency issues are apparent in the reviewed diff.

Deterministic check: success — No issues found

Risk: 2/5 (Low) — raised by: dependency/lockfile change

✅ Auto-approved — Deterministic gates passed: severity thresholds met, recommendation "approve", risk level 2/5 within threshold 3.

---

Token usage: 69,642 input, 1,205 output, 71,448 cache read | Usage Guide

Cooldown: for the next 10 minutes (counting from when this review finished), new pushes to this PR will not trigger another review — the next push after the window expires will. Need a fresh review sooner? Comment @nansen-pr-reviewer[bot] re-review.

[nansen-pr-reviewer]

✅ Auto-approved by Nansen review

Deterministic gates passed: severity thresholds met, recommendation "approve", risk level 2/5 within threshold 3.

• The deterministic severity check passed: No issues found
• Risk level 2/5 (Low)
• The model recommended: approve

Approval was decided by deterministic gates, not by the model. The model's recommendation can block auto-approval but never cause it.

[nansen-pr-reviewer]

✅ Auto-approved by Nansen review

Deterministic gates passed: severity thresholds met, recommendation "approve", risk level 2/5 within threshold 3.

• The deterministic severity check passed: No issues found
• Risk level 2/5 (Low)
• The model recommended: approve

Approval was decided by deterministic gates, not by the model. The model's recommendation can block auto-approval but never cause it.

[nansen-pr-reviewer]

✅ Auto-approved by Nansen review

Deterministic gates passed: severity thresholds met, recommendation "approve", risk level 2/5 within threshold 3.

• The deterministic severity check passed: No issues found
• Risk level 2/5 (Low)
• The model recommended: approve

Approval was decided by deterministic gates, not by the model. The model's recommendation can block auto-approval but never cause it.