NDEV-2081: Upgrade Solana to v1.16.11 #170
Closed
Conversation
This file contains 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
andreisilviudragnea
requested review from
Deniskore,
anton-lisanin and
afalaleev
andreisilviudragnea
force-pushed
the
v1.16
branch
2 times, most recently
from
bc4be29 to
70b1b6a
Compare
andreisilviudragnea
force-pushed
the
v1.16
branch
from
70b1b6a to
0e60947
Compare
andreisilviudragnea
changed the title
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.
DO NOT MERGE THIS YET - kept as a draft PR for tracking purposes
Solana devnet started using
v1.16, which is incompatible withv1.14.20.Solana repository has the following versioning scheme: There is a
masterbranch where current development is happening. From time to time, release branches are created from this branch (e.g.v1.14,v1.16). Some commits from these release branches are tagged with patch versions (e.g.v1.14.20,v.1.16.8).With this PR, I propose a simple versioning scheme for this repo:
developbranch will stay on Solanav1.14until mainnet reachesv1.16toov1.16branch will be used on Solana devnet and testnet and will be rebased overdevelopwhenever new commits are merged todevelopv1.16will be merged todevelopwhen Solanav1.16reaches mainnetThere is currently a bug in Solana
v1.16.8, which pins tokio version used bysolana-clientto~1.14.4(more than a year old), and prevents updating this repo to Solana v1.16.8. Thre is a fix in progress for this problem. Until then, I created this PR using our Solana fork with the patchedv1.16branch.These are the current version floors for each Solana network: https://github.com/solana-labs/solana/wiki/Feature-Gate-Activation-Schedule#version-floor