release: stamp v0.6.0#14
Merged
Merged
Conversation
Cuts 0.6.0 (MINOR) so :latest carries Ask A/B before multis Phase 2 ships (Phase 2 hard-depends on the exact-id echo-guard — no text fallback left). Bundles everything under [Unreleased]: poll_messages watch primitive + source echo-guard (#11), docker-restart stale-lock fix (#12), reliable echo via final-id resolution + supervised backend (#13). - CHANGELOG: [Unreleased] -> [0.6.0] — 2026-06-15 with a release summary. - mcp/server.js: serverInfo.version 0.5.0 -> 0.6.0 (was stale). - docs/PRD.md: status stamp -> v0.6.0; release-history table corrected (the stale "(unreleased)" row is 0.5.1) + 0.6.0 row; example tag bumped. - beeperbox.context.md / README.md: version stamps + pin example -> 0.6.0. Tag v0.6.0 after merge triggers the gated publish (:0.6.0/:0.6/:0/:latest, old :latest -> :previous). Live id-resolution round-trip validated by multis; CI gate still runs the server standalone (no account). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes
[Unreleased]→## [0.6.0] — 2026-06-15so:latestcarries Ask A/B before multis Phase 2 ships (Phase 2 drops_isLooping+ the text-prefix hack and hard-depends on the exact-id echo-guard).Bundled in 0.6.0 (everything from
[Unreleased])poll_messageswatch primitive +source/client_tagecho-guard (feat(mcp): poll_messages watch primitive + source echo-guard #11)docker restartstale-Xvfb-lock fix (fix(entrypoint): clear stale Xvfb lock so docker restart survives #12)pendingMessageID→ final-bridge-id resolution + supervisedbeepertexts(feat: reliable echo via final-id resolution + supervise beepertexts #13)MINOR per the versioning policy: new MCP tool + additive schema fields + new runtime behavior, all backward compatible.
Version stamps moved
mcp/server.js—serverInfo.version0.5.0→0.6.0(was stale even at 0.5.1)docs/PRD.md— status →v0.6.0; release-history table corrected (the stale(unreleased)row was actually 0.5.1) + new 0.6.0 row; example tag bumpedbeeperbox.context.md/README.md— header/version-table stamps + pin example →0.6.0Release mechanics
Merging this is docs-only. The
v0.6.0tag (pushed after merge) is what triggersrelease.ymlto build the gated multi-arch image and publish:0.6.0/:0.6/:0/:latest(old:latest→:previous).Verification note
The
sourceecho-guard and the id-resolution round-trip were validated against a real Beeper account by multis; CI has no account, so the standard release gate (MCP guard matrix + VNC probe) still runs the server standalone. 27/27 unit tests pass.🤖 Generated with Claude Code