Set up crates.io + binary releases: publish-on-tag workflow#2
Merged
Conversation
- Cargo.toml: fix repository URL (codeoid -> saucam org), add homepage +
keywords for crates.io, and pin the internal path-deps to version "0.1.0"
(required for crates.io publishing). Crates inherit homepage/keywords.
- .github/workflows/release.yml: on a v* tag,
(1) publish codeoid-protocol -> codeoid-client -> codeoid-tui to crates.io in
dependency order (cargo waits for each to index), and
(2) build + upload codeoid-tui binaries for macOS arm64/x64 + Linux x64 to a
GitHub Release.
- CHANGELOG.md (0.1.0) + RELEASING.md runbook (add CARGO_REGISTRY_TOKEN, tag).
Validated: cargo check + `cargo publish --dry-run -p codeoid-protocol` pass;
downstream crates can only resolve once protocol is on crates.io, which the
workflow ordering handles.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Merged
saucam
added a commit
that referenced
this pull request
Jul 11, 2026
…r path Coverage top-up #2 for the input-safety PR (84% → ~91% patch): - the reconnect backoff unit is injectable (1s in production, ms in tests), and event_loop/reconnect_with_backoff are generic over the render backend + terminal-event stream — the full 5-attempt budget path and the quit-during-backoff path now run in CI against a dead port on a TestBackend (a stray key is asserted DISCARDED, q quits). - the reader task's cancel-pending guard moved to module scope with a direct drop test (it also covers panic unwinds, which no exit-point call could). - ClientHandle::detached_for_tests() (doc-hidden) lets the TUI exercise request/error paths without a daemon — used to pin "/destroy failed:" surfacing when the socket dies mid-request. Remaining uncovered lines are the live-connection plumbing (run()'s outer reconnect loop, the reconnect success arm, destroy's post-success list refresh) — coverable only with a real WS handshake fixture. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
saucam
added a commit
that referenced
this pull request
Jul 11, 2026
…troy confirm (#18) * fix: never wedge or eat input — request timeouts, prompt restore, destroy confirm Four input-safety fixes for the TUI, all traced from a codebase audit: - requests are now bounded: `ClientHandle::request` times out after 30s (RequestTimeout) and a reader-task Drop guard cancels every pending request the moment the socket dies (RequestCancelled) — previously a `/fork` or `/provider` awaited inside the event loop could freeze the UI forever if the daemon died mid-request, recoverable only by kill -9. - the reconnect backoff now drains terminal input: `q`/Ctrl+C quit during the ~31s backoff window (previously the keyboard was dead the whole time) and stray keystrokes are discarded instead of replaying into the prompt after reconnect. - a slash-command typo or a send with no session no longer destroys the prompt text — the draft is restored alongside the error. - `/destroy` now opens the (previously built but unreachable) ConfirmDestroy modal: `y` destroys — surfacing daemon rejections instead of silently pretending — `n`/Esc cancel, everything else is absorbed so a stray key can't confirm. - the documented `m` cycle-mode key actually works now (was a silent no-op): interactive → guarded → autonomous, starting at interactive when the mode is unknown. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix: cover the request-wrapper and reducer guard branches Patch-coverage top-up for the input-safety changes: the production request() delegation (answered-in-time path), the Action::CycleMode reducer arm, and the /destroy no-session guard. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix: cover the reconnect backoff, reader drop guard, and destroy error path Coverage top-up #2 for the input-safety PR (84% → ~91% patch): - the reconnect backoff unit is injectable (1s in production, ms in tests), and event_loop/reconnect_with_backoff are generic over the render backend + terminal-event stream — the full 5-attempt budget path and the quit-during-backoff path now run in CI against a dead port on a TestBackend (a stray key is asserted DISCARDED, q quits). - the reader task's cancel-pending guard moved to module scope with a direct drop test (it also covers panic unwinds, which no exit-point call could). - ClientHandle::detached_for_tests() (doc-hidden) lets the TUI exercise request/error paths without a daemon — used to pin "/destroy failed:" surfacing when the socket dies mid-request. Remaining uncovered lines are the live-connection plumbing (run()'s outer reconnect loop, the reconnect success arm, destroy's post-success list refresh) — coverable only with a real WS handshake fixture. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- 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.
Second half of release setup (the Rust client). Pairs with codeoid's npm release (saucam/codeoid#20).
What this adds
.github/workflows/release.yml— on avX.Y.Ztag:codeoid-protocol→codeoid-client→codeoid-tuiin dependency order (cargo waits for each to index).codeoid-tuion native runners and upload tarballs for macOS arm64 + x64 and Linux x64 to a GitHub Release.repositoryURL corrected (codeoid/codeoid-ui→saucam/codeoid-ui).version = "0.1.0"— required for crates.io.homepage+keywordsfor the crates.io listing.To cut the release (after merge)
CARGO_REGISTRY_TOKENrepo secret (crates.io API token; binaries use the built-inGITHUB_TOKEN).git tag v0.1.0 && git push origin v0.1.0→cargo install codeoid-tui+ downloadable binaries.Validated:
cargo check+cargo publish --dry-run -p codeoid-protocolpass;Cargo.lockis untouched so the--lockedCI build holds.🤖 Generated with Claude Code