CHANGELOG.md: put missing CHANGELOG entries in for PR 9136.
What the developer wrote
Authored by Rusty Russell
CHANGELOG.md: put missing CHANGELOG entries in for PR 9136.
Removals should be documented with Changelog-Removed lines, mirroring
the old Deprecated line.
In this case, the `max_total_htlc_in_msat` removal was premature: we try
to give one version AFTER the deprecation period.
That way users can re-enable the feature if they need to, using
`--i-promise-to-fix-broken-api-user=listpeerchannels.max_total_htlc_in_msat`
and we can decide whether to defer removal, re-enable, even un-deprecate
(or get whatever tool they are using fixed).
It's happened a few times in the past that nobody tested with deprecations
disabled, and users got stuck when they upgraded :(
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
What changed, and why it matters
This commit only edits the project's CHANGELOG.md file. It adds documentation notes about two previously-merged changes (a plugin notification field and a renamed JSON-RPC value) and a link to a pull request. No code behavior changes, no bug fixes, and no security-related content are present.
No security action needed. Treat as routine documentation maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only update to CHANGELOG.md. It records two removals: (1) the channel_state_changed notification’s message field will be omitted instead of being null, and (2) the listpeerchannels value max_total_htlc_in_msat is removed in favor of our_max_htlc_value_in_flight_msat. The commit message explains that the second removal was premature and that users can re-enable it via a compatibility flag. No source code is modified.
Changed components
CHANGELOG.mdInspect captured patch +3 / −0
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c7ea2a20..79ac2614 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -48,6 +48,8 @@ Note: You should always set `allow-deprecated-apis=false` to test for changes.
### Removed
- JSON-RPC: `exclude` parameter to `pay` (when `xpay-handle-pay` is True): craft a layer with desired modifications and pass it to `xpay` `layers`. ([#9110])
+ - Plugins: `channel_state_changed` notification `message` field being `null`: it will be omitted instead (deprecated v25.12, disabled v26.04) ([#9136])
+ - JSON-RPC: `listpeerchannels` value `max_total_htlc_in_msat`: use `our_max_htlc_value_in_flight_msat` instead to follow spec naming convention (deprecated v25.02). ([#9136])
### Fixed
@@ -95,6 +97,7 @@ Note: You should always set `allow-deprecated-apis=false` to test for changes.
[#9116]: https://github.com/ElementsProject/lightning/pull/9116
[#8942]: https://github.com/ElementsProject/lightning/pull/8942
[#8922]: https://github.com/ElementsProject/lightning/pull/8922
+[#9136]: https://github.com/ElementsProject/lightning/pull/9136
[26.06rc1]: https://github.com/ElementsProject/lightning/releases/tag/v26.06rc1
## [26.04.1] - 2026-04-25: "Negative Routing Fees II"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.