You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
What
Some cloud sessions sync a local git repository or folder with the cloud. Attaching one of these sessions now looks for a signing key belonging to the device the session is bound to. If this machine has no such key, sync stops instead of going ahead. The sync connection only accepts signed updates.
Opening git directory sync refuses in the same way when no key is available.
Why
In practice, a machine without a device key can no longer sync unsigned changes. It stops instead.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich users or sessions this sync feature is available to is not settled.
