From d570bb007a46f1e654f61138347f16aa64191d1c Mon Sep 17 00:00:00 2001 From: Andrew Grimberg Date: Mon, 2 Nov 2026 11:13:11 -0800 Subject: [PATCH] Docs(release): Add note for registry rebuild Part of #893 (#851) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Andrew Grimberg --- .../trust-rebuilt-registry-50a879d4a17ec391.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 releasenotes/notes/trust-rebuilt-registry-50a879d4a17ec391.yaml diff --git a/releasenotes/notes/trust-rebuilt-registry-50a879d4a17ec391.yaml b/releasenotes/notes/trust-rebuilt-registry-50a879d4a17ec391.yaml new file mode 100644 index 0000000..0a580be --- /dev/null +++ b/releasenotes/notes/trust-rebuilt-registry-50a879d4a17ec391.yaml @@ -0,0 +1,12 @@ +--- +fixes: + - | + A corrupt door code registry no longer withholds new door codes + indefinitely on sites where every entry has a lock. Once every entry + with a lock has read its whole slot range, the rebuilt registry is + trusted and issuance resumes. Slots excluded with + ``rental_control.set_slot_exclusion`` count as read, so an excluded + dead slot no longer holds recovery back. A lock that cannot be read + still withholds new codes, and the adoption notification now says + so and names the unreachable lock. Diagnostics list the entries + whose lock or slot range has not been read yet.