fix(release): sandbox 0.2.1 pin and full SDK Meta Harness alignment for 9.0.0 - #179
Merged
Merged
Conversation
…rates.io. The v9.0.0 crates.io publish failed tarball verification: Code was qualified against Sandbox d381943 (apply_network_grant takes &self) while crates.io 0.2.0 still takes &mut self. Sandbox 0.2.1 is d381943 plus a version bump. Co-authored-by: Cursor <cursoragent@cursor.com>
… parity in CI. Go SessionOptions gains Harness (HarnessOptions, HarnessHost, stock part constants) mapped to Core with_harness in the bridge. SDK sessions that set harness now install BuiltinHostHarnessRegistry: no SDK could inject a Rust registry, so documented host:<id> mounts failed closed on the first run. sdk_api_alignment_check now derives Go's required SessionOptions, Session, and Agent surface from Core like Node/Python, with explicit Go alias tables, so a missing Go field or method fails CI and the release workflow. Tests: Go bridge admits host:intent_stamp end to end; Go wire JSON; Node test_meta_harness.mjs and Python test_session_options_harness.py run in sdk-runtime. Co-authored-by: Cursor <cursoragent@cursor.com>
ZhiXiao-Lin
changed the title
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
2 participants
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.
Two blockers for the 9.0.0 cut:
d381943(apply_network_grant(&self)) while crates.ioa3s-sandbox0.2.0 still takes&mut self. This pinsa3s-sandbox =0.2.1at Sandboxrelease/0.2.1(2b86878=d381943+ version bump). Sandbox 0.2.1 must be on crates.io before re-tagging.SessionOptions.Harness; added with bridge mapping.HostHarnessRegistry, so documentedhost:<id>mounts failed closed on the first run from Node, Python, and Go. SDK sessions that setharnessnow installBuiltinHostHarnessRegistry.sdk_api_alignment_check.mjscompared Go against a hand-written list, which is why it missed this. It now derives Go's required SessionOptions/Session/Agent from Core like Node/Python (explicit Go alias tables), so a gap fails CI and release.Tests: Go bridge admits
host:intent_stampend to end; Go wire JSON; Nodetest_meta_harness.mjsand Pythontest_session_options_harness.py(both run in sdk-runtime).