v0.7.0

0.7.0 - 2026-05-15

• Added messenger command surfaces: Telegram BotCommand menus, Discord native /relay command metadata/routing, and Slack /pirelay slash-command manifest and runtime support. #56
• Improved command-surface documentation and setup guidance, including reliable Discord/Slack text fallbacks and archived OpenSpec requirements. #56 #57
• Fixed README command tables so alternatives containing | render correctly. #55

v0.6.0

0.6.0 - 2026-05-15

• Added unified messenger file delivery and requester-scoped remote safe file requests for Telegram, Discord, and Slack. #41 #43
• Hardened revoked and disconnected bindings so stale routes, timers, and duplicate runtimes do not send protected session feedback after disconnect. #44
• Improved stale route/context safety so unavailable sessions remain offline, pairing screens are not closed by stale routes, and prompts, controls, media, and status snapshots use coherent route availability checks. #46 #47 #49
• Centralized binding authority resolution so broker, adapter, and runtime delivery paths consistently suppress stale or unauthorized bindings. #52
• Added OpenSpec designs for approval gates and messenger command surfaces to guide upcoming safe remote-control UX. #15 #51

v0.5.0

PiRelay 0.5.0

• Added lifecycle notifications so paired Telegram, Discord, and Slack conversations are notified when a Pi session goes offline, comes back online, or is disconnected locally. #38
• Improved relay setup and status UX with clearer readiness diagnostics, safer setup reloads, instance-scoped status keys, and paired/paused/error status line states. #36
• Improved Slack runtime UX with safer progress notification handling, readiness checks, App Home guidance, and nonfatal best-effort activity failures. #36
• Fixed Slack shared-room/channel routing so active selections are preserved safely, pirelay to <session> <prompt> works as a one-shot target, and stale selections are pruned after disconnects or runtime stops. #37
• Fixed Telegram setup/config behavior to prefer PI_RELAY_TELEGRAM_BOT_TOKEN over legacy token inputs and surface runtime registration errors accurately. #36

Validation:

• npm run typecheck
• npm test
• npm pack --dry-run
• npm run openspec:validate

v0.4.0

Highlights

• Added full Slack relay adapter/runtime support with Socket Mode ingress, pairing, trust, command handling, shared-room routing, thread context, Block Kit actions, and terminal notifications.
• Added real Slack live integration coverage, app manifests, and testing documentation for driver/bot workflows.
• Added same-host broker namespace isolation for concurrent relay runtimes and live tests.
• Added OpenSpec validation to GitHub CI for active change proposals.
• Improved shared-room parity coverage and hardened messenger shared-room behavior.
• Fixed Telegram shared-room private bindings.

Validation

• npm run typecheck
• npm test
• npm run openspec:validate
• GitHub CI on PR #35 passed for Node 20 and 24.

v0.3.0

Highlights

• Adds shared-room machine bot support for targeting distinct PiRelay machine bots in shared messenger rooms.
• Archives the completed OpenSpec change and syncs shared-room machine bot requirements into the main specs.
• Bumps package metadata to 0.3.0.

Validation

• npm run typecheck
• npm test
• openspec validate --all --strict

v0.2.0

Highlights

• Adds Telegram progress/dashboard support with safe rate-limited updates.
• Adds per-session aliases, recent activity, and dashboard quick actions.
• Improves broker/in-process parity and multi-session UX.
• Updates docs, tests, and OpenSpec archive.

Validation

• npm run typecheck
• npm test
• openspec validate --all --strict

v0.1.0

Full Changelog: https://github.com/zikolach/pirelay/commits/v0.1.0