Root cause
A variable shadowing bug in the disable path chose a resolver list with no user resolvers. Nothing failed, so the missing check stayed silent.
Linear filters data so each member sees only their own teams. On March 24, 2026 a permission optimization shipped, enabled for one internal workspace only. A bug in its disable path exposed private team data for about one hour.
Tests covered the enabled path but not the disabled path.
Requests from web, mobile, and API reach the sync group mechanism. A sync group adds resolvers that filter data to the teams of the user. The optimization skips resolvers that can never match a user.
In the bug, the disable path dropped all user resolvers, and the downstream permission check was skipped without any error.
A variable shadowing bug in the disable path chose a resolver list with no user resolvers. Nothing failed, so the missing check stayed silent.
Clients ran about 7,000 full bootstraps, so data reached local databases. Notification emails showed inflated counts, and some members got a digest of the whole workspace. Notification pruning archived items per workspace, and a feed summary generator wrote cross-team posts.
| No. | Chose | Instead of | Why |
|---|---|---|---|
| D1 | Clear caches, raise the database version, and end sessions | This removed leaked data from client databases. |
| Bootstrap | A full download of data into a client database. |
|---|