Purge the stored rows for the two retired notes rights

FeatureInitializerService
Shipped
15 Agosti 2026, 02:01 UTC
Author
Kamo
Commit
fce1f98

SHARE_NOTES (72) and MANAGE_NOTES_SETTINGS (73) were deleted from RoleRightType today for having no feature to gate. This removes what they left behind, counted and logged in the same run rather than left for RoleRightsSyncService to sweep silently on some later SecurityService boot. Measured before writing it: 84 rows across the role tables, 16 template rows, 94 applied rows, and none at department, job-title or member level. Both encodings again. The rights tables and the applied snapshot store the integer id; **************** stores the enum NAME. One id-keyed DELETE would match nothing on the template table and report success, leaving 16 rows for rights that no longer resolve to be read into the force-rule map on every recalculation — which is not hypothetical, it is what happened to 24 of the 150 rows the chat-channel purge was meant to remove. No seeding and no verification gate, unlike the meet seed: deleting a right cannot remove anybody's access, because nothing ever read these. That is what made them deletable in the first place.

All changes

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei