mirror of
https://github.com/ElementsProject/lightning.git
synced 2026-08-18 13:08:13 +02:00
d732fa9724
The issue is that the new keyword `force_lease_closed` was being set even if the user didn't specify it, which results in breakage if this new pyln version talks to older c-lightning nodes that don't have this keyword yet. By setting the default to `None` it gets filtered out if the user has not explicitly set it, but still retains the `True` / `False` values if they did. Changelog-None Issue is not present in released versions |
||
|---|---|---|
| .. | ||
| init | ||
| keys | ||
| libhsmd_python | ||
| plugins | ||
| pylightning | ||
| pyln-client | ||
| pyln-proto | ||
| pyln-spec | ||
| pyln-testing | ||
| reprobuild | ||
| sanitizer_suppressions | ||
| bootstrap-node.sh | ||
| Dockerfile.builder | ||
| Dockerfile.builder.fedora | ||
| Dockerfile.tester | ||
| lightning-cli.bash-completion | ||
| linuxarm32v7.Dockerfile | ||
| linuxarm64v8.Dockerfile | ||
| short_channel_id-to-txid.sh | ||
| startup_regtest.sh | ||