Release v0.2.1 - #11
Merged
Merged
Conversation
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
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.
Release v0.2.1
Bugfixes
publish-pypi, where it protects the PyPI channel as intended.query_statusthrough the persistent daemon (Route query_status through the persistent daemon #9) — repeat status polls drop from ~30s+ to milliseconds._ensure_daemonpings on every call: a healthy daemon replies in milliseconds, so a slow or failing ping means wedged-or-absent. In that case we shut it down (cooperatively viaPOST /shutdown, falling back toSIGTERM/SIGKILLon the PID viapgrepif the HTTP handler is stuck) and start a fresh one before using it.Misc
docs/llm-integration.mdplus expandedstart_printMCP docstring. Documents thatresult: "sent"withreturn_code: -1/print_result: -999is the success path (not an error), and other quirks an LLM-driven workflow needs to know.Merge this PR to trigger the release pipeline. The release workflow will build the package, validate on TestPyPI (will fail until trusted publishing is configured — but that no longer blocks the rest thanks to #8), create the
v0.2.1tag, create the GitHub Release with the newboocloud-bridge-linux-x86_64binary attached, and skip PyPI publish (gated on the dry-run gate).🤖 Generated with Claude Code