Public commit record
33/100 · Opaque
What the developer wrote
Authored by Rusty Russell
doc: pretty!
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Subject identifies a change✓ Provides an explanatory body! Too few words to establish purpose
What changed, and why it matters
This commit only reformats a documentation table so the columns line up nicely. No code, no behavior, and no security-related changes are present.
Recommended action
No action needed; this is a cosmetic documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a whitespace/formatting-only change to doc/developers-guide/deprecated-features.md. It adjusts Markdown table column widths and alignment without altering any text content, deprecation dates, or feature descriptions.
Changed components
doc/developers-guide/deprecated-features.mdInspect captured patch +16 / −16
diff --git a/doc/developers-guide/deprecated-features.md b/doc/developers-guide/deprecated-features.md
index 6a99ffd3..81455d2a 100644
--- a/doc/developers-guide/deprecated-features.md
+++ b/doc/developers-guide/deprecated-features.md
@@ -5,22 +5,22 @@ excerpt: "Deprecated features and timeline for old feature removals."
hidden: false
---
-| Name | Type | First Deprecated | Last Supported | Description |
-|--------------------------------------|--------------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| listpeers.features.option_anchors_zero_fee_htlc_tx | Field | v24.08 | v25.09 | Renamed to `option_anchors` in the spec: check for that in `features` instead |
-| decodepay | Command | v24.11 | v25.12 | Use `decode` which is more powerful (since v23.05) |
-| close.tx | Field | v24.11 | v25.12 | Use txs array instead |
-| close.txid | Field | v24.11 | v25.12 | Use txids array instead |
-| xpay.ignore_bolt12_mpp | Field | v25.05 | v25.12 | Try MPP even if the BOLT12 invoice doesn't explicitly allow it (CLN didn't until 25.02) |
-| listpeerchannels.max_total_htlc_in_msat | Field | v25.02 | v26.03 | Use our_max_total_htlc_out_msat |
-| wait.details | Field | v25.05 | v26.06 | Use subsystem-specific object instead |
-| channel_state_changed.old_state.unknown | Notification Field | v25.05 | v26.03 | Value "unknown" is deprecated: field will be omitted instead |
-| coin_movement.tags | Notification Field | v25.09 | v26.09 | Use `primary_tag` (first tag) and `extra_tags` instead |
-| coin_movement.utxo_txid | Notification Field | v25.09 | v26.09 | Use `utxo` instead of `utxo_txid` & `vout` |
-| coin_movement.txid | Notification Field | v25.09 | v26.09 | Use `spending_txid` instead |
-| channel_state_changed.null_scid | Notification Field | v25.09 | v26.09 | In channel_state_changed notification, `short_channel_id` will be missing instead of `null` |
-| notification.payload | Notification Field | v25.09 | v26.09 | Notifications from plugins used to have fields in `payload` sub-object, now they are not (just like normal notifications) |
-| pay_notifications.raw_fields | Field | v25.09 | v26.09 | `channel_hint_update`, `pay_failure` and `pay_success` notifications now wrap members in an object of the same name |
+| Name | Type | First Deprecated | Last Supported | Description |
+|----------------------------------------------------|--------------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------|
+| listpeers.features.option_anchors_zero_fee_htlc_tx | Field | v24.08 | v25.09 | Renamed to `option_anchors` in the spec: check for that in `features` instead |
+| decodepay | Command | v24.11 | v25.12 | Use `decode` which is more powerful (since v23.05) |
+| close.tx | Field | v24.11 | v25.12 | Use txs array instead |
+| close.txid | Field | v24.11 | v25.12 | Use txids array instead |
+| xpay.ignore_bolt12_mpp | Field | v25.05 | v25.12 | Try MPP even if the BOLT12 invoice doesn't explicitly allow it (CLN didn't until 25.02) |
+| listpeerchannels.max_total_htlc_in_msat | Field | v25.02 | v26.03 | Use our_max_total_htlc_out_msat |
+| wait.details | Field | v25.05 | v26.06 | Use subsystem-specific object instead |
+| channel_state_changed.old_state.unknown | Notification Field | v25.05 | v26.03 | Value "unknown" is deprecated: field will be omitted instead |
+| coin_movement.tags | Notification Field | v25.09 | v26.09 | Use `primary_tag` (first tag) and `extra_tags` instead |
+| coin_movement.utxo_txid | Notification Field | v25.09 | v26.09 | Use `utxo` instead of `utxo_txid` & `vout` |
+| coin_movement.txid | Notification Field | v25.09 | v26.09 | Use `spending_txid` instead |
+| channel_state_changed.null_scid | Notification Field | v25.09 | v26.09 | In channel_state_changed notification, `short_channel_id` will be missing instead of `null` |
+| notification.payload | Notification Field | v25.09 | v26.09 | Notifications from plugins used to have fields in `payload` sub-object, now they are not (just like normal notifications) |
+| pay_notifications.raw_fields | Field | v25.09 | v26.09 | `channel_hint_update`, `pay_failure` and `pay_success` notifications now wrap members in an object of the same name |
Inevitably there are features which need to change: either to be generalized, or removed when they can no longer be supported.
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.