lnd allows one-field channel fee updates and isolates bad inputs in the sweeper
Two changes merged into lnd, the Lightning Network node software, on 13 and 14 November address problems operators run into when they manage channels and recover funds.
The first, pull request 11528, fixes channel policy updates. UpdateChannelPolicy could not tell an unset base fee, fee rate or time-lock delta from zero, so lncli updatechanpolicy required all three on every call and its help text showed a misleading default of 0. The cause is protobuf: proto3 does not put zero values on the wire, so a request for a zero base fee looks the same as one that omits it. Making unset fields mean "keep the current value" by default would have broken existing clients, so the change is opt-in. A new PartialPolicyUpdate message carries one flag per field; when it is present, only the marked fields are applied, and a non-zero value in an unmarked field is rejected rather than silently ignored. The developers chose a separate message over proto3's optional keyword because that would have turned the generated Go fields into pointers and broken consumers such as lndclient at compile time.
lncli updatechanpolicy now always sends a partial update, so each field can be set on its own. Because an older lnd ignores the new field and could reset a missing fee to 0, the CLI checks the node version first and refuses to send to versions below 0.21.99.
The second change, pull request 10842, concerns the sweeper, which batches inputs into sweep transactions. Until now, if one input caused the mempool to reject a sweep, the healthy inputs in the same batch could not progress. The change runs no-broadcast probes on subsets of the batch to identify an input-specific failure, records its cause, and retries the survivors with a new aggregate fee curve. Rejections caused by replace-by-fee rules or minimum relay and mempool fees are treated as inconclusive, because they do not point to a single input. The description notes that full-RBF fee rejection alone cannot identify a bad input and that TRUC and package validation are outside this change.
A third merge, pull request 10891, removes the staging feature bits 160 and 161 for RBF-based cooperative close, since the final bits 60 and 61 have been in production for a while.

Why it matters
Both main changes remove a way for one value to spoil the rest. In fee policy, a missing field could reset a fee to zero; in sweeping, one problematic input could hold back funds in every other input of the batch. For node operators managing many channels, both make routine maintenance less likely to cause collateral damage.