Skip to content

deps: Bump mollusk-svm to 0.17 - #119

Merged
joncinque merged 1 commit into
solana-program:mainfrom
clankmaxxing-clod:mollusk-0.17
Nov 20, 2026
Merged

joncinque merged 1 commit into
solana-program:mainfrom
clankmaxxing-clod:mollusk-0.17

Conversation

@clankmaxxing-clod

Copy link
Copy Markdown
Contributor

Problem

mollusk-svm is on 0.7.0, and the latest release is 0.17.1.

Summary of changes

  • Bump mollusk-svm from 0.7.0 to 0.17.1, and update Cargo.lock with cargo update -p mollusk-svm.
  • Mollusk 0.17 uses solana-account 5, so bump that dev-dependency from 3 to 5.
  • Toolchains: Mollusk 0.17 depends on agave 4.4, which requires Rust 1.98.1, so rust-toolchain.toml goes from 1.86.0 to 1.98.1. The pinned nightly in the Makefile and Cargo.toml goes from nightly-2025-02-16 to nightly-2026-07-16.
  • Solana CLI: the Makefile pin goes from 2.3.4 to 4.3.2, and workspace.metadata.cli from 3.0.0 to 4.3.2. The updated lockfile contains edition-2024 crates (e.g. wincode-derive 0.5), and the Cargo bundled with the 2.3.4 platform tools can't parse them, so cargo build-sbf fails. That's the same failure token hit in deps: Bump mollusk crates to 0.17 token#203.

No source changes were needed.

Testing

Locally:

  • make build-sbf-program with Solana CLI 4.3.2
  • make test-{interface,program}
  • make clippy-* with the new nightly
  • cargo fmt --check and make audit

🤖 Generated with Claude Code

Mollusk 0.17 uses solana-account 5 and depends on agave 4.4, which
requires rustc 1.98.1. Bump the matching test dependency and toolchains.

The updated lockfile contains edition-2024 crates, which the Cargo bundled
with Solana CLI 2.3.4's platform tools can't parse, so bump the CLI to
4.3.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@joncinque
joncinque merged commit 09f03ae into solana-program:main Nov 20, 2026
24 checks passed
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.

2 participants