v0.31.7

The peppy platform commands are rebuilt around workspaces, projects, and enrolling machines in a project's cloud router.

Released on October 1, 2026

peppy platform list is removed; peppy platform peers now lists a project's router peers, with columns for peer name, status, certificate expiry, and id.
PEPPY_API_KEY personal-access-token authentication is removed; sign in with peppy platform login instead.
The zenoh.managed.federation block (with connect_timeout_secs) is gone from peppy_config.json5; remove it or the daemon refuses to load the config.
peppy platform status now reports this machine's enrollment and router link; use peppy platform whoami for the signed-in identity.
Run peppy platform login again after upgrading, because the previous credentials file is no longer read.

peppy platform login signs you in and then enrolls this machine in a project's cloud router, with --workspace, --project, and --no-enroll to steer it.
peppy platform enroll joins an already-signed-in machine to a project, --replace mints a fresh identity, and peppy platform unenroll removes it (--local-only deletes only the local record).
Enrolling or unenrolling restarts the daemon under the new identity and wipes the running node stack, prompting first unless you pass --yes.
The daemon renews the peer certificate automatically while you stay signed in, so an enrolled machine keeps its cloud-router link without manual steps.
peppy platform logout revokes the session and clears the selection but leaves the machine enrolled, so the daemon stays connected until its certificate expires.

peppy platform workspace and peppy platform project (each with show, list, use, and clear) pick the default workspace and project the other commands act on.
peppy platform router restart applies pending changes such as a removed peer, and peppy platform router start starts a stopped router.