-
Notifications
You must be signed in to change notification settings - Fork 91
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
Update BDK to 1.0.0 and LDK to 0.1.0 #426
Conversation
aa745c6
to
115104c
Compare
115104c
to
4e31967
Compare
Rebased on #429 to check it works (as other CI failures are fixed here). |
4e31967
to
d7eb1a1
Compare
d7eb1a1
to
363dd0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Feel free to squash fixups.
363dd0f
to
d7e3d67
Compare
Squashed. I think we'll still need to wait |
d7e3d67
to
b8b9f01
Compare
Previously, we decided to continue parsing any fields if we failed to parse a known (i.e., `lightning` or `lno`) parameter failed to parse. This however just hides the error and is a bit anti-idiomatic even though allowing to use *some* URI fields even in the face of incompatible formats for others. Here we therefore opt to fail parsing the URI if any field fails.
b8b9f01
to
c39bfba
Compare
@jkczyz Now updated the branch for final 0.1.0 release crates, and dropped the |
We upgrade LDK and BDK to the latest releases.