v0.0.110.1

• Updated to LDK-C-Bindings 0.0.110.1, adding several new getters
• Added getters for channel and node lists from
  lightningdevkit/rust-lightning#1651
• Fixed numerous memory corruption or crash bugs in TS bindings
• Supported lock structs in TS bindings
• Reduced log verbosity in TS bindings

v0.0.110.0

No significant bindings changes since 0.0.108.1.
See upstream release notes at
https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.110

v0.0.109.0

No significant bindings changes since 0.0.108.1.
See upstream release notes at
https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.109

v0.0.108.0

No material bindings-specific changes, see upstream release notes at
https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.107
and
https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.108

v0.0.106.0

Upstream release notes available at https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.106

Bindings-specific changes are minimal.

0.0.105.1

This exposes the ProbabilisticScorer added in 0.0.105 which was missing in 0.0.105.0

v0.0.105.0

No significant changes to bindings themselves, see upstream release notes for 0.0.105.for changes.

v0.0.104.1

No substantial changes on the Java end, initial TypeScript support is
still in-flight.

Only substantial change is a lockorder fix backported from the
(upcoming) 0.0.105 release. See
lightningdevkit/rust-lightning#1238 for more
details.

v0.0.104.0

• Updates to LDK version 0.0.104. See
  https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.104
  for the full changelog.
• Use Reference.reachabilityFence to work around Java's somewhat
  poorly documented memory model. This seems to be the intended use so
  its likely this will fix the early finalization bugs we've seen, but
  formal documentation on the Java memory model appears to be lacking
  so its possible (albeit unlikely) that more may be required later.
  This bumps our required Java version from 1.8 to 9.
• Exposes Hash and Eq via Java's hashCode and equals.
• Thows an exception instead of incorrect operation if multiple
  ChannelMonitors for the same channel are provided to a
  ChannelManagerConstructor.

v0.0.103.1

Based on LDK v0.0.103 and LDK-C-Bindings v0.0.103.1, this fixes a number
of minor (and a few major) issues in the Java bindings.

• Exposes the full Logger interface to Java, with information on
  severity and module which originated the log call.
• Expose read on MaybeReadable objects (like Event) which may or
  may not read an object which was written (some Events are not
  written to disk).
• Include documentation from Rust on enum variants.
• Allow specifying a UserConfig object in both
  ChannelManagerConstructor constructors.
• Check array lengths for constant-length arrays (like keys and block
  headers) prior to calling into Rust. This avoids undefined behavior
  (often a crash) when a byte array of incorrect length is passed.
• Provide a new is_ok method on Result types instead of requiring
  matching of the object's type.
• Include missing functions on 3-tuples.
• Resolve a rare use-after-free when returning an object from a Java
  interface method that was called from Rust.
• Increase pointer validity checking in leaktracking builds.
• Resolve a NullPointerException when calling trait methods on a Rust
  instance of a trait which was wrapped in an Option.