What changed, and why it matters
This commit only reformats the release notes markdown file. It changes how a list of pull request links is displayed (from bullet points to a single bracketed list) with no changes to code, configuration, or documentation content. There is no security relevance.
No action needed. This is a documentation formatting change with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a pure formatting change in docs/release-notes/release-notes-0.20.0.md. It converts two bulleted lists of PR links into inline comma-separated bracketed lists. No functional text, code, schemas, queries, migrations, or RPC behavior is modified.
Changed components
Inspect captured patch +15 / −15
diff --git a/docs/release-notes/release-notes-0.20.0.md b/docs/release-notes/release-notes-0.20.0.md
index ddf8509..1f8fe23 100644
--- a/docs/release-notes/release-notes-0.20.0.md
+++ b/docs/release-notes/release-notes-0.20.0.md
@@ -149,22 +149,22 @@ circuit. The indices are only available for forwarding events saved after v0.20.
* Only [fetch required
fields](https://github.com/lightningnetwork/lnd/pull/9923) during graph
cache population.
- * Add graph schemas, queries and CRUD:
- * [1](https://github.com/lightningnetwork/lnd/pull/9866)
- * [2](https://github.com/lightningnetwork/lnd/pull/9869)
- * [3](https://github.com/lightningnetwork/lnd/pull/9887)
- * [4](https://github.com/lightningnetwork/lnd/pull/9931)
- * [5](https://github.com/lightningnetwork/lnd/pull/9935)
- * [6](https://github.com/lightningnetwork/lnd/pull/9936)
- * [7](https://github.com/lightningnetwork/lnd/pull/9937)
- * [8](https://github.com/lightningnetwork/lnd/pull/9938)
- * [9](https://github.com/lightningnetwork/lnd/pull/9939)
- * [10](https://github.com/lightningnetwork/lnd/pull/9971)
- * [11](https://github.com/lightningnetwork/lnd/pull/9972)
+ * Add graph schemas, queries and CRUD:
+ [[1](https://github.com/lightningnetwork/lnd/pull/9866),
+ [2](https://github.com/lightningnetwork/lnd/pull/9869),
+ [3](https://github.com/lightningnetwork/lnd/pull/9887),
+ [4](https://github.com/lightningnetwork/lnd/pull/9931),
+ [5](https://github.com/lightningnetwork/lnd/pull/9935),
+ [6](https://github.com/lightningnetwork/lnd/pull/9936),
+ [7](https://github.com/lightningnetwork/lnd/pull/9937),
+ [8](https://github.com/lightningnetwork/lnd/pull/9938),
+ [9](https://github.com/lightningnetwork/lnd/pull/9939),
+ [10](https://github.com/lightningnetwork/lnd/pull/9971),
+ [11](https://github.com/lightningnetwork/lnd/pull/9972)]
* Add graph SQL migration logic:
- * [1](https://github.com/lightningnetwork/lnd/pull/10036)
- * [2](https://github.com/lightningnetwork/lnd/pull/10050)
- * [3](https://github.com/lightningnetwork/lnd/pull/10038)
+ [[1](https://github.com/lightningnetwork/lnd/pull/10036),
+ [2](https://github.com/lightningnetwork/lnd/pull/10050),
+ [3](https://github.com/lightningnetwork/lnd/pull/10038)]
## RPC Updates
* Previously the `RoutingPolicy` would return the inbound fee record in its
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.