solana-sdk: deprecate modules migrated to agave #94
Conversation
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
This was referenced Mar 27, 2025
joncinque
approved these changes
Mar 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The following
solana_sdkmodules should no longer be consumed by anyone and are now marked as deprecatedprecompilesfeature_setreserved_account_keysBoth the
feature_setandreserved_account_keyswere attempted to be marked as deprecated in the past but adding deprecation annotations to a re-export of a crate does not work. This change puts those re-exports inside a deprecated module so that consumers actually receive the deprecation notice. The other broken deprecation annotations are left as an exercise to anyone who cares to fix it ;)