Repository navigation
deps: Bump mollusk crates to 0.17 - #203
Merged
Merged
Conversation
Mollusk 0.17 depends on agave 4.4, so bump the test dependencies that share types with it: solana-account 5 in both programs, and agave 4.4 / solana-transaction 5 / solana-signer 4 / solana-keypair 4 for the pinocchio program's program-test suite. API changes picked up along the way: * `Check::all_rent_exempt()` is gone; Mollusk now runs rent-state checks by default. * Mollusk's `feature_set` is now an `SVMFeatureSet`. * `Rent::lamports_per_byte_year` is renamed to `lamports_per_byte`. * `InstructionError` now comes from solana-instruction-error. * `solana_account::create_account_for_test` is gone; use Mollusk's `keyed_account_for_rent_sysvar` instead. * `Account::new` is deprecated; use `Account::new_with_data`. Also point five8 1.0.0 at five8_core 1.0.0 in the lockfile, since solana-keypair 4 needs `DecodeError: Error`, which five8_core 0.1 lacks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The updated lockfile now includes edition-2024 crates (e.g. zeroize_derive 1.5), which the Cargo 1.84 shipped with the 3.0.0 platform tools can't parse, so `cargo build-sbf` fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
joncinque
approved these changes
Nov 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
mollusk-svmandmollusk-svm-fuzz-fixtureare on 0.11, and the latest release is 0.17.1.Summary of changes
Bump
mollusk-svmandmollusk-svm-fuzz-fixturefrom 0.11.0 to 0.17.1.Mollusk 0.17 depends on agave 4.4, which uses newer major versions of several SDK crates. These dev-dependencies are bumped to match:
program:solana-account3 → 5pinocchio/program:solana-account3 → 5,solana-program-testandagave-feature-set3 → 4.4.1,solana-transaction3 → 5,solana-transaction-error3 → 4,solana-keypairandsolana-signer3 → 4,solana-rent3 → 4.4, plus a newsolana-instruction-error3 dependencyAPI changes between Mollusk 0.11 and 0.17, and in the newer SDK crates:
Check::all_rent_exempt()was removed because Mollusk now checks rent-state transitions by default (anza-xyz/mollusk#317). The calls inbatch.rsare removed, and the check still runs.Mollusk::feature_setis now anSVMFeatureSet, sobatch.rsusesFeatureSet::all_enabled().runtime_features().solana-rent4 renamedRent::lamports_per_byte_yeartolamports_per_byte(sync_native.rs).InstructionErroris imported fromsolana-instruction-error, becausesolana-instruction'serrormodule no longer provides it.solana_account::create_account_for_testno longer exists. The rent sysvar account inprogram/tests/processor.rsnow comes from Mollusk'sSysvars::default().keyed_account_for_rent_sysvar().Account::newis deprecated insolana-account5.2. The 107 test call sites now useAccount::new_with_data(lamports, vec![0; space], owner), which creates the same zero-filled account. Otherwise clippy with-D warningsfails.Cargo.lock: besides thecargo update, thefive81.0.0 entry now points atfive8_core1.0.0 instead of 0.1.2.five81.0.0 acceptsfive8_core >=0.1.1, <2, and the resolver reused the older 0.1.2. That version'sDecodeErrordoesn't implementError, sosolana-keypair4.0.1 failed to compile.cargo metadata --lockedaccepts the edited lockfile.Makefile:SOLANA_CLI_VERSIONgoes from 3.0.0 to 4.3.2, the same version token-2022 uses. The updated lockfile includes edition-2024 crates (e.g.zeroize_derive1.5), and the Cargo 1.84 shipped with the 3.0.0 platform tools can't parse them, socargo build-sbffailed in CI. This also moves the JS tests' local validator to 4.3.2.Apart from the CLI version, only tests, dev-dependencies and
Cargo.lockchange; neither program's own dependencies are touched.Testing
Locally:
make build-sbf-programandmake build-sbf-pinocchio-programwith Solana CLI 4.3.2make test-{interface,pinocchio-interface,pinocchio-program,program}--features mollusk-svm/fuzzmake clippy-*for all four packages withnightly-2026-07-16cargo fmt --checkandmake auditI didn't run the
mollusk run-testregression job. It uses the fixtures checked into the repo and the latestmollusk-svm-cli, so this bump doesn't affect it.🤖 Generated with Claude Code