smtp fixes database replays but strips key safeguards
One useful installation fix is bundled with removals that could break fresh deployments and weaken data protections.
smtp has made an older set of database updates safer to replay from scratch, preventing setup failures when a later change has already removed information an earlier update expected to find.
But the same change removes several newer database updates without explanation, including protections and features for:
- Audit logging, including restrictions on who can read those records.
- Narrower high-privilege access, limiting damage if credentials leak.
- Microsoft Word chat support and workflow changes.
- User-record integrity and consistent project-sharing email addresses.
The application still appears to rely on some of the removed pieces. That means a new installation could have broken audit or Word-related features, while an existing deployment may lose important access controls.
Teams maintaining a Mike deployment should borrow the replay-safety idea, but avoid these deletions until smtp explains or restores them.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?