Skip to content

Version Packages - #836

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

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.6.1

Patch Changes

  • #834 c2e511e Thanks @kome12! - nansen schema and shell completion now list the type-specific filter options of alerts create and alerts update (flow thresholds, token, sector, market cap, FDV, event, value and subject filters), with the alert types each one applies to.

  • #835 197996b Thanks @kome12! - wallet send --dry-run from a Privy wallet now rejects a malformed, zero or too-small SPL token amount on Solana, as the real send does, instead of previewing it as a success.

  • #837 478eab1 Thanks @kome12! - nansen alerts create and update no longer offer the smart-contract-call alert type, which the Nansen API retired and now rejects. Passing --type smart-contract-call, or one of the flags only that type used (--signature-hash, --caller, --contract, --exclude-caller, --exclude-contract), now fails with an INVALID_PARAMS error that says the type was retired, before any request is sent. An unknown --type value is rejected the same way, with the valid types listed. nansen schema now lists the valid --type values as an enum.

@nansen-pr-reviewer

nansen-pr-reviewer Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

nansen-pr-reviewer summary

This is a release-only version bump from 2.6.0 to 2.6.1, with the three consumed changesets moved into CHANGELOG.md and package-lock.json kept in sync. No runtime, dependency, workflow, schema, or trading logic changes are present.

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: 130,560 input, 1,065 output, 24,791 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[bot]
nansen-pr-reviewer Bot previously approved these changes Nov 13, 2026

@nansen-pr-reviewer nansen-pr-reviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 54704af to 65ce842 Compare November 15, 2026 23:38

@nansen-pr-reviewer nansen-pr-reviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants