build(deps): bump lightning-persister from 0.0.123 to 0.0.125

[dependabot]

Bumps lightning-persister from 0.0.123 to 0.0.125.

Release notes

Sourced from lightning-persister's releases.

v0.0.125

0.0.125 - Oct 14, 2024 - "Delayed Beta Testing"

Bug Fixes

• On upgrade to 0.0.124, channels which were at a steady-state (i.e. for which the counterparty has received our latest revoke_and_ack message) will force-close upon receiving the next channel state update from our counterparty. When built with debug assertions a debug assertion failure will occur instead (#3362).
• Listeners in a ChainListenerSet will now have their block_connected method called, when appropriate, rather than always having their filtered_block_connected method called with full block data (#3354).
• Routefinding historical liquidity channel scores were made more consistent for channels which have very little data which has been decayed (#3362).
• A debug assertion failure when adding nodes to the network graph after removal of nodes from the network graph was fixed (#3362).

In total, this release features 6 files changed, 32 insertions, 7 deletions in 5 commits since 0.0.124 from 2 authors, in alphabetical order:

• Elias Rohrer
• Matt Corallo

v0.0.124

0.0.124 - Sep 3, 2024 - "Papercutting Feature Requests"

API Updates

• rust-bitcoin has been updated to 0.32. The new bitcoin-io crate is now used for all IO traits, irrespective of the features set on LDK crates. LDK crates no longer automatically force features on dependent crates where possible, allowing different std/no-std settings between LDK and rust-bitcoin crates (e.g. to disable std on LDK to ensure system time is not accessed while using bitcoin-io's std feature). (#3063, #3239, #3249).
• A new lightning_types crate was added which contains various top-level types. Using types from lightning::ln::features or Payment{Hash,Preimage,Secret} from lightning::ln or lightning::ln::types is now deprecated. The new crate is re-exported as lightning::types (#3234, #3253).
• lightning now depends on lightning-invoice, rather than the other way around. The lightning_invoice::payment module has moved to lightning::ln::bolt11_payment and lightning_invoice::utils to lightning::ln::invoice_utils (#3234).
• Event handlers may now return errors, causing most events to be replayed immediately without blocking the background processor. See documentation on individual Events for more information on replay (#2995).
• ChannelDetails::balance_msat is deprecated in favor of ChainMonitor::get_claimable_balances and the Balance, which now contains substantially more details and more accurately calculates a node-wide balance when Balance::claimable_amount_satoshis are summed (#3212, #3247).
• ConfirmationTarget has two new variants - a MaximumFeeEstimate which can

... (truncated)

Changelog

Sourced from lightning-persister's changelog.

0.0.125 - Oct 14, 2024 - "Delayed Beta Testing"

Bug Fixes

• On upgrade to 0.0.124, channels which were at a steady-state (i.e. for which the counterparty has received our latest revoke_and_ack message) will force-close upon receiving the next channel state update from our counterparty. When built with debug assertions a debug assertion failure will occur instead (#3362).
• Listeners in a ChainListenerSet will now have their block_connected method called, when appropriate, rather than always having their filtered_block_connected method called with full block data (#3354).
• Routefinding historical liquidity channel scores were made more consistent for channels which have very little data which has been decayed (#3362).
• A debug assertion failure when adding nodes to the network graph after removal of nodes from the network graph was fixed (#3362).

In total, this release features 6 files changed, 32 insertions, 7 deletions in 5 commits since 0.0.124 from 2 authors, in alphabetical order:

• Elias Rohrer
• Matt Corallo

0.0.124 - Sep 3, 2024 - "Papercutting Feature Requests"

API Updates

• rust-bitcoin has been updated to 0.32. The new bitcoin-io crate is now used for all IO traits, irrespective of the features set on LDK crates. LDK crates no longer automatically force features on dependent crates where possible, allowing different std/no-std settings between LDK and rust-bitcoin crates (e.g. to disable std on LDK to ensure system time is not accessed while using bitcoin-io's std feature). (#3063, #3239, #3249).
• A new lightning_types crate was added which contains various top-level types. Using types from lightning::ln::features or Payment{Hash,Preimage,Secret} from lightning::ln or lightning::ln::types is now deprecated. The new crate is re-exported as lightning::types (#3234, #3253).
• lightning now depends on lightning-invoice, rather than the other way around. The lightning_invoice::payment module has moved to lightning::ln::bolt11_payment and lightning_invoice::utils to lightning::ln::invoice_utils (#3234).
• Event handlers may now return errors, causing most events to be replayed immediately without blocking the background processor. See documentation on individual Events for more information on replay (#2995).
• ChannelDetails::balance_msat is deprecated in favor of ChainMonitor::get_claimable_balances and the Balance, which now contains substantially more details and more accurately calculates a node-wide balance when Balance::claimable_amount_satoshis are summed (#3212, #3247).
• ConfirmationTarget has two new variants - a MaximumFeeEstimate which can help to avoid spurious force-closes by ensuring we always accept feerates up

... (truncated)

Commits

• e80d632 Merge pull request #3362 from TheBlueMatt/2024-10-0.0.125
• 2028c78 Add CHANGELOG entry for 0.0.125
• f0f1b22 Bump crate versions to 0.0.125
• a6834eb Fix docs.rs for crates which depend on lightning w/o features
• e48074a Don't interpret decayed data as we've failed to send tiny values
• a675d48 Fix synchronize_listeners calling default implementation
• acfc6d9 Don't bump the next_node_counter when using a removed counter
• 68d27bc Set holder_commitment_point to Available on upgrade
• b023eed Merge pull request #3278 from TheBlueMatt/2024-08-124-relnotes
• c9de257 Update versions to 0.0.124 and invoice 0.32 types 0.1 release
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.