Bump spl-tlv-account-resolution to 0.11.3 - #138
Merged
Conversation
…xamples
The weekly Anchor v1 run on 31 August failed in two projects, transfer-cost
and allow-block-list-token, both at `anchor build`:
Compiling spl-list-view v0.1.0
error[E0277]: `?` couldn't convert the error to `ProgramError`
--> src/list_view.rs:104:38
Neither project names spl-list-view. Both depend on
spl-tlv-account-resolution "0.11.1", and 0.11.2, published on 26 August,
added spl-list-view 0.1.0 as a dependency. That crate was written in February
against spl-pod 0.7.2, whose `PodLength` fixed the `TryFrom<usize>` error type
to `PodSliceError`. spl-pod 0.7.3 in April dropped that constraint, so
`L::try_from(..)?` no longer had a `From` impl to go through, and spl-list-view
0.1.0 has not compiled against a fresh resolution since. Nothing here pulled it
in until 0.11.2 appeared, and the scheduled run was the first fresh resolution
after that.
Upstream fixed it within hours of the run: spl-list-view 0.1.1, spl-pod 0.7.4
and spl-tlv-account-resolution 0.11.3 all shipped on 31 August, and 0.11.3
requires spl-list-view 0.1.1. A fresh resolution today lands on 0.11.3 and
both programs build; the re-run of the failed jobs confirms it.
Nothing in this repository was wrong, so the change is a floor, not a fix:
requiring 0.11.3 means a lockfile generated between the 26th and the 31st
cannot keep the broken pair after `cargo update`, and the comment records why
the number is what it is. The other transfer-hook examples pin the 0.9 line,
which never depended on spl-list-view.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015wh3nRzs8oAUpNbCY97gDi
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Updates the
spl-tlv-account-resolutiondependency from 0.11.1 to 0.11.3 across multiple transfer hook programs to resolve a transitive dependency compatibility issue.Changes
spl-tlv-account-resolutionversion constraint in:tokens/token-extensions/transfer-hook/allow-block-list-token/anchor-v1/programs/abl-token/Cargo.tomltokens/token-extensions/transfer-hook/transfer-cost/anchor-v1/programs/transfer-hook/Cargo.tomlDetails
Version 0.11.2 of
spl-tlv-account-resolutionintroduced a transitive dependency onspl-list-view 0.1.0, which was incompatible withspl-pod 0.7.3due to a breaking change in thePodLengthtrait's error type. This caused compilation failures in lockfiles created during the window before the upstream fix. Version 0.11.3 resolves this incompatibility and was released the same day as thespl-podupdate. Setting the floor to 0.11.3 ensures past this broken dependency pair.https://claude.ai/code/session_015wh3nRzs8oAUpNbCY97gDi