v0.26.5

Opening a workspace wrote the member's name and email address into Workers Logs. Updating a self-hosted copy needs no
migration and no new setting, and the protocol stays at version 25. (#203)

Fixed

• People's names and addresses reached the logs. The request that opens a workspace's socket carried the member's
  whole profile in a header, and Workers Logs records that request's headers for seven days, so anyone who can read a
  deployment's logs could read them. It now carries only the person's id, and the gateway hands over the profile first
  by RPC, whose arguments are not logged. What is already in the logs ages out by itself. (#203)

Upgrading

During the deploy, a tab can reach an old gateway with a new object or the other way round. Its socket is refused and it
reconnects, as with any deploy. A gateway you changed yourself must call syncMember before opening a socket, and send
the member's id rather than their profile.