Skip to content

v3.10.0

Choose a tag to compare

@github-actions github-actions released this 25 Jul 17:22
· 29 commits to main since this release
Immutable release. Only release title and notes can be modified.

Share a link, not a process β€” a shellshare room now outlives the command that created it.

πŸ€– dmesg | shellshare --json finally works. A room used to be deleted the moment the broadcast ended, so a command that finished quickly printed a link that was already dead, and the only way around it was padding the pipe with sleep 600. Rooms now stay up until they go idle (6 hours on shellshare.net), so a one-second command still leaves a link people can open β€” and your script gets its prompt back immediately instead of babysitting a process. The same goes for exec and for an interactive shell you've exited. One consequence worth knowing: a room name stays claimed for as long as the room lives, so another machine asking for that name is turned away until it expires.

πŸ” Rerunning a named room starts clean. Now that your room survives, shellshare -r deploy-log twice in a row would have stacked the second run underneath the first. It doesn't: a new session clears whatever the room was holding, including for anyone who left the tab open β€” their screen resets rather than growing a seam. The share link itself is unchanged, so a link you handed out earlier keeps working.

πŸ“‘ A quiet broadcast no longer looks dead. Piping a log that goes silent for a while β€” journalctl -f on an idle unit, a build between phases β€” used to flip viewers to "offline" after 90 seconds, and could lose the room out from under a broadcast that was still perfectly alive. Piped broadcasts now keep their connection alive while idle, and a room with someone still broadcasting is never expired.

What's Changed

Full Changelog: v3.9.0...v3.10.0