tlv account resolution: bump #5985
Merged
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
|
ah ok, I'll likely have to republish token-2022 to pick up this change. cargo / semver considers 0.4 and 0.5 to be incompatible, so it won't work |
joncinque
approved these changes
Dec 11, 2023
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.
In step with #5970 we need to bump the TLV Account Resolution library.
Note: I think I semi-bungled this a bit. I published
spl-transfer-hook-interface, which was using the previous version of TLV Account Resolution, however it does not use any of the new version0.5.0code.The example, however, does use the new code, so it requires version
0.5.0.If both are used together, Cargo should resolve to
0.5.0all the time, right?