Add a pending changelog entry to note new backwards incompat
What the developer wrote
Authored by Matt Corallo
Add a pending changelog entry to note new backwards incompat
What changed, and why it matters
This commit only adds a changelog note warning users that two newly introduced payment options will prevent downgrading to version 0.2 while a payment is in progress. There is no code change, no bug fix, and no security issue in the commit itself.
No security action required. Treat as a routine documentation/changelog commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff creates a pending changelog file stating that setting OptionalBolt11PaymentParams::declared_total_mpp_value_override or RecipientOnionFields::total_mpp_amount_msat breaks downgrade compatibility to rust-lightning 0.2 until the payment completes. This is purely documentation of an intentional backwards-compatibility behavior.
Changed components
pending_changelog/4373.txtInspect captured patch +4 / −0
diff --git a/pending_changelog/4373.txt b/pending_changelog/4373.txt
new file mode 100644
index 0000000..e606063
--- /dev/null
+++ b/pending_changelog/4373.txt
@@ -0,0 +1,4 @@
+## Backwards Compat
+ * Setting `OptionalBolt11PaymentParams::declared_total_mpp_value_override` or
+ `RecipientOnionFields::total_mpp_amount_msat` for a payment will break
+ downgrade to 0.2 until the payment completes.
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.