Repository navigation
deps: Bump agave/solana version to support V1 transactions - #3
Merged
petarvujovic98 merged 4 commits intoSep 23, 2026
Merged
petarvujovic98 merged 4 commits into
petarvujovic98 merged 4 commits into
Conversation
Yiwen-Gao
approved these changes
Sep 23, 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.

TL;DR
Upgrades
wincodeto0.6,solana-reward-infoto7.0.0, and addsbank_idsupport introduced in agave 4.3.What changed?
wincodefrom0.5to0.6.1across all dependent crates. Most crates continue to resolve to0.5.5, while the top-level workspace now uses0.6.1.solana-reward-infofrom version6to7.0.0in the workspace, with select crates pinned to6.2.0where required.socket2(0.5→0.6),itertools(0.13→0.14),syn(1→2),rand_core(0.5→0.6),tokio-util(0.6→0.7).bank_idparameter (introduced in agave 4.3) tonotify_transaction,notify_entry, andSlotNotification::Rootcalls in the firehose geyser thread. Since the firehose replays finalized history with one bank per slot, the slot is used as a stable unique identifier in place of a distinct bank ID.firehose_geysertest fixture to include the additionalu64::MAXargument matching the newbank_idparameter.How to test?
Run the existing test suite to verify the firehose geyser integration continues to function correctly. Confirm that block, transaction, and entry notifications are emitted as expected when replaying finalized history.
Why make this change?
Agave 4.3 introduced a
bank_idfield to disambiguate banks across forks in the notification interfaces. This change brings the firehose implementation into compliance with that updated API while using the slot as the bank ID, which is a safe assumption given that the firehose only processes finalized, single-bank-per-slot history.