f missing things and more details

Author: TheBlueMatt

CHANGELOG.md

@@ -9,13 +9,15 @@
    and receiving (via a new `RecipientOnionFields` struct) (#2139, #2127).
  * `Event::PaymentFailed` now exposes a failure reason (#2142).
  * BOLT12 messages now support stateless generation and validation (#1989).
- * Max HTLCs in-flight is now configurable via `our_max_accepted_htlcs` (#2138).
+ * The `NetworkGraph` is now pruned of stale data after RGS processing (#2161).
+ * Max inbound HTLCs in-flight can be changed in the handshake config (#2138).
  * `lightning-transaction-sync` feature `esplora-async-https` was added (#2085).
- * A `ChannelPending` event was added (#2098).
- * `PaymentForwarded::amount_forwarded_msat` was added (#2136).
+ * A `ChannelPending` event is now emitted after the initial handshake (#2098).
+ * `PaymentForwarded::outbound_amount_forwarded_msat` was added (#2136).
  * `ChannelManager::list_channels_by_counterparty` was added (#2079).
- * `ChannelDetails::feerate_per_kw` was added (#2094).
+ * `ChannelDetails::feerate_sat_per_1000_weight` was added (#2094).
  * `Invoice::fallback_addresses` was added to fetch `bitcoin` types (#2023).
+ * The offer/refund description is now exposed in `Invoice{,Request}` (#2206).
 
 ## Backwards Compatibility
  * Payments sent with the legacy `*_with_route` methods on LDK 0.0.115+ will no
@@ -40,8 +42,11 @@
  * Fixed compilation of `lightning-invoice` with both `no-std` and serde (#2187)
  * Fix an issue where the `background-processor` would not wake when a
    `ChannelMonitorUpdate` completed asynchronously, causing delays (#2090).
+ * Fix an issue where `process_events_async` would exit immediately (#2145).
  * `Router` calls from the `ChannelManager` now call `find_route_with_id` rather
    than `find_route`, as was intended and described in the API (#2092).
+ * Ensure `process_events_async` always exits if any sleep future returns true,
+   not just if all sleep futures repeatedly return true (#2145).
  * `channel_update` messages no longer set the disable bit unless the peer has
    been disconnected for some time. This should resolve cases where channels are
    disabled for extended periods of time (#2198).
@@ -52,10 +57,10 @@
 ## Security
  * Transaction re-broadcasting is now substantially more aggressive, including a
    new regular rebroadcast feature called on a timer from the
-   `background-processor` or directly from the `ChainMonitor`. This should
-   substantially increase transaction confirmation reliability without relying
-   on downstream `TransactionBroadcaster` implementations for rebroadcasting
-   (#2203, #2205, #2208).
+   `background-processor` or from `ChainMonitor::rebroadcast_pending_claims`.
+   This should substantially increase transaction confirmation reliability
+   without relying on downstream `TransactionBroadcaster` implementations for
+   rebroadcasting (#2203, #2205, #2208).
  * Implemented the changes from BOLT PRs #1031, #1032, and #1040 which resolve a
    privacy vulnerability which allows an intermediate node on the path to
    discover the final destination for a payment (#2062).