0.21.0

v0.21.0

4 changes · 2 Bugfixes, 1 New Feature, 1 Chore · 3 points.

Bugfix

• RADD-784 a successor also inherits the deleted account's memberships and role grants _{auth security · 3 pts · 6ca23b87} Found while fixing RADD-783, which was the loud instance of this class.
• RADD-862 release_notes.py clobbers the section page's body on every run _{ci docs · 447ac154} What's wrong. _find_or_create_page PATCHes the body whenever it differs — correct for the VERSION pages (re-running a tag must update its changelog), wrong for the structural root/section pages: the 0.20.0 publish reset "Release notes" to its hardcoded one-liner, silently deleting the radd:children embed fence…

New Feature

• RADD-846 LDAP connection is env-only: URL, bind account and admin groups should be editable on Settings → Directory _{auth ldap settings ux · 5e7551cd} What's wrong. The LDAP connection — server URL, user domain, bind DN, bind password, admin groups — lives only in RADD_LDAP_* env vars, read at process start. The Settings → Directory page can edit search bases and sync toggles (spec 85) but not the connection itself, so "LDAP sign-in: off" is a fact an admin can…

Chore

• RADD-844 decide: does being a participant confer item visibility (a participant relation)? _{access auth items · 55b37ebb} What's wrong. Spec 72 participants were designed when every active user read every item (the old Baseline), so "share my ticket with a colleague" only ever drove notifications — visibility came free. RADD-825 narrowed the floor to item.read@own, and now sharing a ticket with someone who holds no read on the project…

Changes from v0.20.0 to v0.21.0.

---

Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.