fix(client,ci): migrate agentos-client to current secure-exec wire API + unblock release pipeline#1608
Open
NathanFlurry wants to merge 2 commits into
Open
Conversation
The committed .github/refs/secure-exec was bumped (PRs #1598-1600) without re-fitting agentos-client, which was last re-fit (d4cbe82) for the older secure-exec 0bf7dcb. Re-fit against the current wire API: - wire::PackageDescriptor { name, dir, acp_entrypoint } -> { dir } (the sidecar reads name/acpEntrypoint from the package manifest at dir) - READ_DIR entries are now list<GuestDirEntry> -> project each .name - handle new ResponsePayload::{GuestKernelResultResponse, ResourceSnapshotResponse} - JsRuntimeConfig gained high_resolution_time
…op stale website filter - verify the secure-exec crate via the crates.io sparse index (the v1 API now returns 403 under crates.io's data-access policy) - install wasm-pack in the publish-npm job so @rivet-dev/agentos-browser's build:dist-wasm (wasm-pack build agentos-sidecar-browser) works - drop the turbo --filter='!@agentos/website' (website is excluded from the workspace, so the filter matches no package and turbo errors)
|
🚅 Deployed to the agentos-pr-1608 environment in agentos
🚅 Environment agentos-pr-1608 in rivet-frontend has no services deployed. |
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.
Reconciles agent-os with the secure-exec it targets and unblocks the release pipeline. Companion secure-exec PR: rivet-dev/secure-exec#267 (agent pack bin fix + crates.io fixture path).
Client wire-API migration (the release blocker)
agentos-clientwas a regression: the committed.github/refs/secure-execwas bumped (chore(deps): bump secure-exec ref to per-binary cmd entry point #1598–1600) without re-fitting the client, whose last re-fit (d4cbe82) targeted the older secure-exec0bf7dcb. It no longer compiled against the ref'd secure-exec.PackageDescriptor→{ dir };READ_DIRentries →GuestDirEntry.name; handle the newResponsePayload::{GuestKernelResultResponse, ResourceSnapshotResponse}variants; addJsRuntimeConfig.high_resolution_time. Keeps main's newer client features (listMounts / readdirEntries / listSoftware).Release-pipeline CI fixes
@rivet-dev/agentos-browser'sbuild:dist-wasmworks.--filter='!@agentos/website'turbo filter (website is excluded from the workspace, so the filter matched no package and turbo errored).Notes on leaked "do-not-commit" workarounds on main (context, addressed operationally)
crates/agentos-sidecar-browserworkspace member and the browser wasm build now work becausesecure-exec-sidecar-browserwas published to crates.io and wasm-pack is installed in CI.website-excluded-from-workspace workaround is worked around by dropping the turbo filter above.Pi agent adapter
createSession("pi")→Cannot find module '/unknown/pi-sdk-acp'failure is fixed by the secure-exec pack change (feat: add durable storage MVP #267): agentbinnow points at the real entry file, so published agents keep their entrypoint. Verified: the adapter now boots and runs.@anthropic-ai/sdk— the snapshot-restored adapter'srequirebase doesn't include the package'snode_modules. That's a secure-exec runtime fix (require resolution must follow the entrypoint symlink to the package's node_modules, like#225did for module-mode).