Skip to content

Upgrade to LDK 0.2 #462

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

Draft
wants to merge 30 commits into
base: main
Choose a base branch
from

Conversation

tnull
Copy link
Collaborator

@tnull tnull commented Feb 6, 2025

No description provided.

@tnull tnull marked this pull request as draft February 6, 2025 15:24
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch 3 times, most recently from 822bd94 to c7b7464 Compare May 21, 2025 12:16
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch 3 times, most recently from 5c97913 to 528d7cc Compare May 29, 2025 14:25
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch 2 times, most recently from 572ff55 to a12ceaf Compare June 3, 2025 12:08
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from a12ceaf to 627a453 Compare June 12, 2025 14:37
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from 627a453 to b341b76 Compare June 23, 2025 06:21
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from 9f3285f to c7483f8 Compare June 30, 2025 13:36
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from c7483f8 to 3232202 Compare July 9, 2025 14:10
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from 3232202 to bbfea66 Compare July 18, 2025 08:31
tnull added 12 commits July 31, 2025 09:11
As part of the version v0.3 release we switched to the upstreamed
`OutputSweeper` which slightly changed our serialization format, having
us run a migration step on startup for backwards compatibility ever
since. Here we drop the migration code running on startup, for
simplicity's sake, but also because it's going to be async going forward
and we currently don't have a runtime available on startup (which might
change soon, but still).

As the v0.3 release now well over a year ago, it's very unlikely that
there are any v0.2 (or even v0.3) users left. If there are any affected
users left, they'll first have to upgrade to any version pre-v0.7,
startup, and then upgrade to v0.7 or later.
.. as having them in two places doesn't make sense
.. we now apply the LSPS2 client-side overrides on a per-counterparty
basis, not as soon as we act as an LSP client
@tnull tnull force-pushed the 2025-02-upgrade-to-ldk-0.2 branch from bbfea66 to 0cd3b4c Compare July 31, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants