-
Notifications
You must be signed in to change notification settings - Fork 76
Tracking issue for upcoming breaking changes #84
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
Comments
Is it possible to release a patch update for solana-sdk still? I'd like to land this: #94 |
Yes, we'll do some patch releases to mark everything as deprecated before doing the breaking release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
Now that the sdk is decoupled from agave, we have a lot more freedom to make breaking changes in individual crates.
However, there are still a lot of users of the omnibus crates
solana-sdk
andsolana-program
, and although we can simply stop updating them ever again, that would cause a lot of churn for downstream developers.This issue aims to bundle together all of the breaking changes for the next breaking release of
solana-sdk
andsolana-program
.Deprecations
solana-feature-set-interface
crate #99Breaking changes in solana-program
std::error::Error
withcore::error::Error
#116js
Cargo feature flag for WASM builds #118Breaking changes in solana-sdk
All the changes in solana-program, plus:
InstructionError
#74solana_sdk::transaction_context
module #95The text was updated successfully, but these errors were encountered: