What changed, and why it matters
This commit only adds a release notes entry describing a previously fixed bug in the `lncli unlock` command. The actual code change was made in a different pull request. There is no functional change in this commit, so it does not introduce or fix a security issue by itself.
No action needed for this documentation-only commit. Review PR #10536 separately if assessing the underlying fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/release-notes/release-notes-0.21.0.md to document PR #10536, which fixed a timing issue where lncli unlock could send the unlock request before the wallet was ready during slow database initialization. This commit is purely documentation and contains no code changes.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index a98a4eb..f9a869d 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -69,6 +69,12 @@
channel that was only expected to be used for a single message. The erring
goroutine would block on the second send, leading to a deadlock at shutdown.
+* [Fixed `lncli unlock` to wait until the wallet is ready to be
+ unlocked](https://github.com/lightningnetwork/lnd/pull/10536)
+ before sending the unlock request. The command now reports wallet state
+ transitions during startup, avoiding lost unlocks during slow database
+ initialization.
+
# New Features
- Basic Support for [onion messaging forwarding](https://github.com/lightningnetwork/lnd/pull/9868)
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.