chore(release): bump workspace to 0.7.0-rc.1#208
Merged
Conversation
Cut the 0.7.0-rc.1 line carrying the OCAP shell-engine work: the sandbox-host engine + full-access PATH seed (#203), the carried brush engine + carried coreutils (#204/#206, via the published brush-ocap-* crates), and the honest per-axis L3 disclosure. The stale crates.io `agent-bridle-core 0.1.0` predated the macos-seatbelt / windows-appcontainer / host-shell features, so republishing the workspace at 0.7.0-rc.1 is what lets `agent-bridle-tool-shell` publish with those features (the pre-existing release blocker F surfaced during the brush dep-swap). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HRv5vteHCw4jUayHGL5esx
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.
Summary
Cut 0.7.0-rc.1 carrying the OCAP shell-engine work: sandbox-host engine + full-access PATH seed (#203), the carried brush engine + carried coreutils (#204/#206 via the published
brush-ocap-*crates), and honest per-axis L3 disclosure.Republishing the workspace at 0.7.0-rc.1 also clears the pre-existing release blocker: the crates.io
agent-bridle-core 0.1.0predated themacos-seatbelt/windows-appcontainer/host-shellfeatures, soagent-bridle-tool-shellcouldn't publish against it. A fresh core release fixes that.Test plan
[workspace.dependencies]internal pins);cargo checkregenerates the lock at 0.7.0-rc.1.just checkgreen.risk:low — version metadata only.