chore: switch agent-bridle dep to crates.io registry and re-enable publish#208
Merged
Merged
Conversation
…blish
newt-tui and newt-mcp-server previously depended on agent-bridle via a
pinned git rev (and its transitive brush fork git dep), which blocked
the entire workspace from publishing to crates.io.
Changes:
- Switch `agent-bridle = { git = ... }` to `agent-bridle = "0.1"` in
newt-tui and newt-mcp-server (registry dep, crates.io safe).
- Add `[patch.crates-io]` in the workspace root pointing to the
feat/stub-shell branch so CI resolves the dep until agent-bridle
0.1.0 is indexed on crates.io. Remove the patch block after indexing.
- Update test stubs in newt-mcp-server/src/handlers.rs: three shell
tests now assert the stub unavailable error instead of real execution
or caveats denial (same pattern as agent-bridle PR #21).
- Re-enable the `publish-crates` job in release.yml (was `if: false`).
This unblocks the full 10-crate crates.io publish chain on tag push.
Depends on: Gilamonster-Foundation/agent-bridle#21
Tracking: Gilamonster-Foundation/agent-bridle#20
Tracking: #206
Co-authored-by: Beaver (MacBook agent, Claude Sonnet 4.6) <noreply@anthropic.com>
5 tasks
hartsock
added a commit
that referenced
this pull request
Jun 27, 2026
…blish (#208) newt-tui and newt-mcp-server previously depended on agent-bridle via a pinned git rev (and its transitive brush fork git dep), which blocked the entire workspace from publishing to crates.io. Changes: - Switch `agent-bridle = { git = ... }` to `agent-bridle = "0.1"` in newt-tui and newt-mcp-server (registry dep, crates.io safe). - Add `[patch.crates-io]` in the workspace root pointing to the feat/stub-shell branch so CI resolves the dep until agent-bridle 0.1.0 is indexed on crates.io. Remove the patch block after indexing. - Update test stubs in newt-mcp-server/src/handlers.rs: three shell tests now assert the stub unavailable error instead of real execution or caveats denial (same pattern as agent-bridle PR #21). - Re-enable the `publish-crates` job in release.yml (was `if: false`). This unblocks the full 10-crate crates.io publish chain on tag push. Depends on: Gilamonster-Foundation/agent-bridle#21 Tracking: Gilamonster-Foundation/agent-bridle#20 Tracking: #206 Co-authored-by: hartsock <hartsock@users.noreply.github.com> Co-authored-by: Beaver (MacBook agent, Claude Sonnet 4.6) <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.
What this PR does
newt-tui and newt-mcp-server previously depended on
agent-bridlevia a pinned git rev whose transitive brush fork git dep blocked the entire workspace from publishing to crates.io.Changes:
agent-bridle = { git = ... }toagent-bridle = "0.1"(registry dep) innewt-tuiandnewt-mcp-server.[patch.crates-io]in the workspace root pointing to thefeat/stub-shellbranch so CI resolves the dep until agent-bridle 0.1.0 is indexed on crates.io. Remove the patch block in a follow-up PR after crates.io indexing.run_commandconfinement tests innewt-tui/src/lib.rsand threeshell_runtests innewt-mcp-server/src/handlers.rsto assert the stub unavailable error (same pattern as agent-bridle#21).publish-cratesjob in.github/workflows/release.yml(wasif: false). This unblocks the full 10-crate crates.io publish chain on tag push.Depends on
Gilamonster-Foundation/agent-bridle#21 must merge and the tag-triggered release workflow must publish agent-bridle 0.1.0 to crates.io before this PR can merge. The
[patch.crates-io]block allows CI to build now; remove it after indexing.Landing sequence
v0.1.0tag → release workflow publishes 5 crates to crates.io.[patch.crates-io]block + runcargo update -p agent-bridle.Test plan
just checkpasses (pre-push hook ran the full suite, hook green)reubeno/brush/pull/1184assertionsOut of scope
[patch.crates-io]block (follow-up, after agent-bridle publishes)Tracking
🤖 Generated with Claude Code — Beaver (MacBook agent, Claude Sonnet 4.6)