Release v0.5.0 (Machines over SSH) #73

Goal

Prepare and cut localhost v0.5.0 — Machines over SSH (PR #67 + docs #70 already on main at 0ac7595; README badge #71 merged after; main HEAD ~206758e).

This issue tracks the release checklist. A prep PR (chore/release-0.5.0) should land first; do not tag, merge the prep PR without Marcel's ok, or publish until he says so.

What's in 0.5.0

• Machines: add a remote via Host from ~/.ssh/config or user@host:port in Settings → Machines; its Projects appear in the sidebar; start/stop/restart/logs as on this computer.
• Open in Browser forwards the remote Port over SSH to the same port on loopback here.
• Uses the system ssh (keys, agent, config, ProxyJump, Tailscale); no passwords; never trusts a host key for you.
• Clear connection errors; auto-reconnect (including after Mac wake); quitting warns about Machines' Services.
• Old background core names its version and asks you to quit it.

See site/src/content/changelog/0.5.0.md (currently released: false, date already 2026-11-05).

Prep PR checklist (chore/release-0.5.0)

• Read RELEASING.md and .github/workflows/release.yml. Confirm where the app version actually comes from (tag vs changelog vs tauri.conf.json / Cargo / etc.). Explain why tauri.conf.json can still say 0.1.0 and server.json 0.2.0 while the published app is 0.4.0.
• Bump version to 0.5.0 only where the release process actually requires it.
• Flip changelog 0.5.0 to released: true with date 2026-11-05; keep Machines/SSH description accurate.
• Confirm docs example Connected · localhost 0.5.0 in site/src/content/docs/machines.md (and related comments/fixtures) matches.
• Decide whether @getlocalhost/cli / server.json (currently 0.2.0) need a bump — only if the CLI or MCP surface changed since 0.2.0. Explain the decision in the PR.
• State clearly in the PR body whether merging to main auto-triggers a release or not (and what does).
• Run relevant local builds/tests; push branch; open PR to main. Do not merge. Do not tag.

Post-merge (Marcel only, after ok)

Per RELEASING.md:

1. Confirm CI green on main.
2. Optionally run Linux packages workflow by hand on the release commit.
3. Tag v0.5.0 and push the tag → Release workflow drafts the GitHub Release.
4. Smoke-test the draft artifacts; Publish release.
5. Publishing re-runs Release → Homebrew cask bump on marcellosso/homebrew-tap.
6. If CLI was bumped: run publish-cli / npm publish, then MCP registry (mcp-publisher publish) as needed.

Out of scope for the prep agent

• No tagging, no GitHub Releases, no push to main, no merge, no npm publish, no Homebrew push, no MCP directory submit.