Release v0.2.2 - #13
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
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.
Release v0.2.2
Bugfixes
_kill_local_daemonnow records the spawned daemon PID in a file ($XDG_RUNTIME_DIR/boocloud-bridge.pidor a per-user temp file) and reads it back to target the exact process. This removes the hard dependency onpgrep, which is missing from slim container images likepython:3.12-slim. Thepgreplookup is kept as a fallback for daemons started outside_start_daemon. Windows force-kill is a safe no-op (Windows uses Docker per the README).Merge to trigger the release pipeline. The workflow will create tag
v0.2.2, publish the GitHub Release, and build + attach the bridge binaries.🤖 Generated with Claude Code