f update release notes

Author: TheBlueMatt

CHANGELOG.md

@@ -17,10 +17,6 @@
    `ChannelMonitor`s (#2359).
  * Batch funding of outbound channels is now supported using the new
    `ChannelManager::batch_funding_transaction_generated` method (#2486).
- * `ChannelDetails::balance_msat` has been removed. Inclusion criteria for that
-   balance was generally unexpected and led to surprising values. Instead, use
-   sum of `ChainMonitor::get_claimable_balances(..).claimable_amount_satoshis()`
-   and HTLC balances (#2476).
  * `ChannelManager::send_preflight_probes` has been added to probe a payment's
    potential paths while a user is providing approval for a payment (#2534).
  * Fully asynchronous `ChannelMonitor` updating is available as an alpha
@@ -40,7 +36,7 @@
  * `LockableScore` now supports read locking for parallel routefinding (#2197).
  * `ChannelMonitor::get_spendable_outputs` was added to allow for re-generation
    of `SpendableOutputDescriptor`s for a channel after they were provided via
-   `Event::SpendableOutputs` (#2609).
+   `Event::SpendableOutputs` (#2609, #2624).
  * `[u8; 32]` has been replaced with a `ChannelId` newtype for chan ids (#2485).
  * `NetAddress` was renamed `SocketAddress` (#2549) and `FromStr` impl'd (#2134)
  * HTLC information is now provided in `Event::PaymentClaimed::htlcs` (#2478).
@@ -79,11 +75,14 @@
    * Then ensure all `ChannelMonitorUpdate`s stored are fully applied to the
      relevant `ChannelMonitor`,
    * finally, write each full `ChannelMonitor` using your new `Persist` impl.
- * `ChannelDetails` serialized with versions of LDK >= 0.0.117 will have their
-   `balance_msat` field set to `next_outbound_htlc_limit_msat` when read by
-   versions of LDK prior to 0.0.117 (#2476).
 
 ## Bug Fixes
+ * Anchor channels which were closed by a counterparty broadcasting its
+   commitment transaction (i.e. force-closing) would previously not generate a
+   `SpendableOutputs` event for the `to_local` (i.e. non-HTLC-encumbered)
+   balance. Those with such balances available should fetch the missing
+   `SpendableOutputDescriptor`s using the new
+   `ChannelMonitor::get_spendable_outputs` method (#2605).
  * Anchor channels HTLC claims on-chain previously spent the entire value of any
    HTLCs as fee, which has now been fixed (#2587).
  * `ChannelManager::send_spontaneous_payment_with_retry` spuriously did not
@@ -121,19 +120,25 @@
 
 ## Security
 0.0.117 fixes several loss-of-funds vulnerabilities in anchor output channels,
-support for which was added in 0.0.116. In addition, it fixes a potential
-loss-of-funds issue when accepting channel(s) from counterparties which are
-miners and using the coinbase transaction's outputs to fund the channel.
+support for which was added in 0.0.116, in reorg handling, and when accepting
+channel(s) from counterparties which are miners.
  * When a counterparty broadcasts their latest commitment transaction for a
-   channel, we'd previously fail to build claiming transactions against any
-   HTLC outputs in that transaction. This could lead to loss of funds if the
-   counterparty is able to eventually claim the HTLC after a timeout (#2606).
+   channel with anchor outputs, we'd previously fail to build claiming
+   transactions against any HTLC outputs in that transaction. This could lead
+   to loss of funds if the counterparty is able to eventually claim the HTLC
+   after a timeout (#2606).
+ * If a channel is closed via an on-chain commitment transaction confirmation
+   with a pending outbound HTLC in the commitment transaction, followed by a
+   reorg which replaces the confirmed commitment transaction with a different
+   (but non-revoked) commitment transaction, all before we learn the payment
+   preimage for this HTLC, we may previously have not generated a proper
+   claiming transaction for the HTLC's value (#2623).
  * 0.0.117 now correctly handles channels for which our counterparty funded the
    channel with a coinbase transaction. As such transactions are not spendable
    until they've reached 100 confirmations, this could have resulted in
    accepting HTLC(s) which are not enforcible on-chain (#1924).
 
-up to date as of 6016101ac8ff31275f31f68eef8d33e94b19c0b1
+up to date as of 620244dc2ec3153a61e009b80a8c59cf41514482
 XXX: add diff statas
 
 # 0.0.116 - Jul 21, 2023 - "Anchoring the Roadmap"