docs: update release notes

This commit is contained in:
yyforyongyu
2024-04-26 02:42:14 +08:00
parent d0441a2a29
commit db52e7e381

View File

@ -342,14 +342,6 @@ bitcoin peers' feefilter values into account](https://github.com/lightningnetwor
add coin selection strategy option to the following on-chain RPC calls
`EstimateFee`, `SendMany`, `SendCoins`, `BatchOpenChannel`, `SendOutputs`, and `FundPsbt`.
* Previously when callng `SendCoins`, `SendMany`, `OpenChannel` and
`CloseChannel` for coop close, it is allowed to specify both an empty
`SatPerVbyte` and `TargetConf`, and a default conf target of 6 will be used.
This is [no longer allowed](
https://github.com/lightningnetwork/lnd/pull/8422) and the caller must
specify either `SatPerVbyte` or `TargetConf` so the fee estimator can do a
proper fee estimation.
* `BumpFee` has been updated to take advantage of the [new budget-based
sweeper](https://github.com/lightningnetwork/lnd/pull/8667). The param
`force` has been deprecated and replaced with a new param `immediate`, and a
@ -421,6 +413,18 @@ bitcoin peers' feefilter values into account](https://github.com/lightningnetwor
manage the lifecycle of the inputs.
## Breaking Changes
* Previously when callng `SendCoins`, `SendMany`, `OpenChannel` and
`CloseChannel` for coop close, it is allowed to specify both an empty
`SatPerVbyte` and `TargetConf`, and a default conf target of 6 will be used.
This will [no longer be
allowed](https://github.com/lightningnetwork/lnd/pull/8422) in the next
release (v0.19.0) and the caller must specify either `SatPerVbyte` or
`TargetConf` so the fee estimator can do a proper fee estimation. For current
release, [an error will be
logged](https://github.com/lightningnetwork/lnd/pull/8693) when no values are
specified.
## Performance Improvements
* Watchtower client DB migration to massively [improve the start-up