Ever Gauzy vs Remote

Ten releases landed inside roughly seven hours, and most of them are security or release-engineering work rather than product. Named advisories were fixed across upload handling, secret masking, and help-center sorting, invite acceptance was pinned to the trusted role to close a privilege escalation, an SSRF-safe agent was shared from core to cover Zapier delivery, and reset, magic, invite, and OAuth tokens are now strictly single-use. In parallel the desktop update path was rebuilt — a dead DigitalOcean Spaces CDN retired in favor of the GitHub feed, with gated Windows Authenticode signing wired up. The one clear product feature is per-tenant, per-domain inbound email capture with its settings surface.

This is a codebase being audited and remediated in one concentrated push, with cherry-picks cascading between develop and stage fast enough that several tags carry identical continuous integration entries and no user-visible change. The pattern — token single-use enforcement, upload allowlists, SSRF-safe fetching, secret masking, signed desktop updates — reads as working through an advisory list rather than responding to one incident. Feature work is continuing underneath it, but it is being outpaced by remediation and release plumbing.

Expect the version number to keep climbing quickly on tags that contain only cherry-picks and CI changes until the stage cascade settles. Once remediation clears, the inbound email capture and documents pipeline work is the most likely area to resume, since both received real feature commits during the sprint.