Skip to content

Releases: lightningdevkit/ldk-garbagecollected

v0.0.121.3

20 Mar 16:21
e434f3b

Choose a tag to compare

  • Fixes an issue where Windows binaries were mangled by llvm-strip
  • Fixes an issue in C# where arrays of strings were handled
    incorrectly
  • Fixes an issue where Java bindings would crash if the first access
    to LDK was a unitary enum
  • Updates upstream LDK to include two backported fixes

v0.0.118.2

15 Mar 15:18

Choose a tag to compare

Backport upstream LDK persistence fix

v0.0.117.2

15 Mar 15:57

Choose a tag to compare

Backport upstream LDK persistence fix

v0.0.118.1

11 Mar 02:51

Choose a tag to compare

Backport upstream LDK Route serialization fixes

v0.0.121.2

07 Mar 14:39
cb6890a

Choose a tag to compare

Includes macOS support for C# bindings

v0.0.121.1

07 Mar 14:40

Choose a tag to compare

Fix Windows heap freeing in C# bindings.

v0.0.117.1

19 Feb 22:49

Choose a tag to compare

  • Re-build of existing 0.0.117 bindings with a backport of the Route
    serialization round-trip fixes.

v0.0.121.0

29 Jan 19:41

Choose a tag to compare

  • C# trait/interfaces were fixed to ensure they are not GC'd prior
    to being called.
  • Updated to LDK 0.0.121

v0.0.118.0

30 Oct 23:25
981f682

Choose a tag to compare

In addition to the upstream LDK 0.0.118 changes, this release bumps to
minimum required glibc version to 2.36. Users on previous versions of
glibc are encouraged to reach out and let us know your requirements.

v0.0.117.0

10 Oct 06:47
d48ed4f

Choose a tag to compare

In addition to the changes in upstream LDK 0.0.117, this release
includes:

  • a substantial change to generated types to use the C type names
    rather than the Rust type names,
  • adding a number of missing @Nullable annotations in Java and
    correcting equivalent | null type definitions in TypeScript,
  • fixing a longstanding bug where supertraits of supertraits were not
    properly accessed after fetching the original trait from Rust,
  • and fixing an error where strings containing unicode codepoints above
    0xFFFF resulted in a panic in Rust due to failure to map from Java's
    "Modified UTF-8" to Rust's enforcement of correct UTF-8.