-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(pyth-solana-receiver-sdk): enable solana-program >= 2 (and thus anchor-lang 0.31.0) #2504
Merged
tejasbadadare
merged 1 commit into
main
from
tb/pyth-solana-receiver-sdk/enable-solana-v2
Mar 20, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually anchor people recommend against having
solana-program
here and encourage using the reexport inanchor_lang::solana_program
, can you try that for the sdkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw that in the migration notes, (and its in my cursed WIP PR).
This is tricky because we use the
pubkey!
macro in lib.rs, but this comes from the solana-program crate, not the reexport. See here: coral-xyz/anchor#3021Their conclusion was just to have consumers specify a solana-program in their Cargo.toml and rely on dependency resolution to figure it out.
Later on they added the macro to the anchor prelude, but this isn't available in 0.28.0, which we need to support due to the other packages in the workspace that need 0.28.0 and have a path dependency on the SDK.
We could publish v0.6.0 of the SDK which enforces anchor-lang>=0.31 and uses the reexport, and then have the workspace programs depend on 0.5.0 of the SDK rather than the path dependency. But of course this removes some of the utility of having the workspace. I think its okay in this case to explicitly depend on solana-program>=1.16.0, especially since we don't use anything that broke in v2.