Repository navigation
build: migrate to btcd v2 modules - #255
Merged
Merged
Conversation
2 tasks
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
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.
Migrate Faraday's Bitcoin types to the btcd v2 modules so it can build with the dependency graph used by Loop #1199.
Use lndclient v0.21.0-3 and the matching v2-compatible dependencies, and align build images and CI with Go 1.26. Exported Bitcoin Go types change.
Use lnd revision
f2963ce1fd19, which contains the released v0.21.4 forwarding-response recovery and replay fixes, rather than the older v2 snapshot. Align the SQL, queue, and result-helper modules with that revision and build with Go 1.26.8.Validation: the repository's unit-test package set passes with the race detector, excluding
/itestas the Makefile does. The separate Faraday integration harness requires its own running nodes.