What changed, and why it matters
This commit only edits the project's Changelog.md file, adding two missing entries that describe fixes already made elsewhere. There are no code changes in this commit itself, so it cannot introduce or fix any security issue directly.
No action needed for this commit. Review the actual code changes in PR #7449 if assessing the security of the referenced Core Lightning fee fixes.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only update to Changelog.md, inserting two bullet points about Core Lightning fee-related fixes (PR #7449). No source code, configuration, or build files are modified. Any security relevance would belong to the original fixes referenced by the changelog entries, not to this changelog update.
Changed components
Changelog.mdInspect captured patch +2 / −0
diff --git a/Changelog.md b/Changelog.md
index 994f20d..02aac1a 100644
--- a/Changelog.md
+++ b/Changelog.md
@@ -30,6 +30,8 @@
* Fix Custom Range formatting in the date range selector (#7439) @NicolasDorier
* Fix Core Lightning compatibility issues (#7449) @NicolasDorier
* Fix Boltcards payments @NicolasDorier
+* Fix Core lightning fundchannel feerate by passing NBitcoin FeePerK value directly as perkb. (#7449) @thgO-O
+* Fix c-lightning MaxFeePercent being sent to xpay in satoshi instead of millisatoshi (#7449) @TowyTowy
* Fix the `Mark as seen` button in the notification list (#7424) @NicolasDorier
* Fix incorrect date range filtering across DST boundaries (#7424) @NicolasDorier
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.