-
Notifications
You must be signed in to change notification settings - Fork 517
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
[Feature]: Upgrade to Borsh 0.10.3 #1152
Comments
Blocked by the same problem with anchor 0.28 and Solana 1.16.5 |
Blocked by same problem! Hopefully someone will prioritize this? it is slowing down the whole Solana community building products on top of Metaplex 😞 |
Neither Solana nor Metaplex nor anyone else should be making these kind of breaking changes in minor versions as it causes a lot of dependency issues, as you've observed. Solana is working on fixing some of the issues on their end and once the fixes are merged Metaplex will be able to bump Solana version to 1.16. See also this issue I created for more context on some of the dependency issues in the ecosystem. |
@samuelvanderwaal I noticed your comment on my PR -- are you sure that PR fixes all of your issues? Or are there other types missing? We're only doing |
I'll have to investigate; I should have some time to try bumping things this week and see if anything else is missing. Thanks for the heads up! |
@joncinque We are in the process of bumping Solana version to |
This has been addressed in this PR: metaplex-foundation/mpl-token-metadata#29 A new Token Metadata crate has been published ( |
Which package is this feature request for?
All
Feature
Current library (all programs) are incompatible with Borsh 0.10.3. This is stopping developers from using latest Solana & Anchor versions.
Standard Change?
No
Ideal solution or implementation
Refactor code to meet new Borsh 0.10.3 standards.
Alternative solutions or implementations
No response
Other context
Getting the following compiling errors when using your library on latest Solana 1.16 or Anchor 0.28.0 versions:
The text was updated successfully, but these errors were encountered: