Replace the public persistent-sandbox contract with workspace-first naming across CLI, SDK, MCP, payloads, and on-disk state. Rename the task surface to workspace equivalents, switch create-time seeding to `seed_path`, and store records under `workspaces/<workspace_id>/workspace.json` without carrying legacy task aliases or migrating old local task state. Keep `pyro run` and `vm_*` unchanged. Validation covered `uv lock`, focused public-contract/API/CLI/manager tests, `UV_CACHE_DIR=.uv-cache make check`, and `UV_CACHE_DIR=.uv-cache make dist-check`.
3.5 KiB
3.5 KiB
Changelog
All notable user-visible changes to pyro-mcp are documented here.
2.4.0
- Replaced the public persistent-workspace surface from
task_*toworkspace_*across the CLI, Python SDK, and MCP server in one clean cut with no compatibility aliases. - Renamed create-time seeding from
source_pathtoseed_pathfor workspace creation while keeping laterworkspace sync pushimports onsource_path. - Switched persisted local records from
tasks/*/task.jsontoworkspaces/*/workspace.jsonand updated the main docs/examples to the workspace-first language.
2.3.0
- Added
task sync pushacross the CLI, Python SDK, and MCP server so started task workspaces can import later host-side directory or archive content without being recreated. - Reused the existing safe archive import path with an explicit destination under
/workspace, including host-side and guest-backed task support. - Documented sync as a non-atomic update path in
2.3.0, with delete-and-recreate as the recovery path if a sync fails partway through.
2.2.0
- Added seeded task creation across the CLI, Python SDK, and MCP server with an optional
source_pathfor host directories and.tar/.tar.gz/.tgzarchives. - Seeded task workspaces now persist
workspace_seedmetadata so later status calls report how/workspacewas initialized. - Reused the task workspace model from
2.1.0while adding the first explicit host-to-task content import path for repeated command workflows.
2.1.0
- Added the first persistent task workspace alpha across the CLI, Python SDK, and MCP server.
- Shipped
task create,task exec,task status,task logs, andtask deleteas an additive surface alongside the existing one-shot VM contract. - Made task workspaces persistent across separate CLI/SDK/MCP processes by storing task records on disk under the runtime base directory.
- Added per-task command journaling so repeated workspace commands can be inspected through
pyro task logsor the matching SDK/MCP methods.
2.0.1
- Fixed the default
pyro env pullpath so empty local profile directories no longer produce broken cached installs or contradictory "Pulled" / "not installed" states. - Hardened cache inspection and repair so broken environment symlinks are treated as uninstalled and repaired on the next pull.
- Added human-mode phase markers for
pyro env pullandpyro runto make longer guest flows easier to follow from the CLI. - Corrected the Python lifecycle example and docs to match the current
exec_vm/vm_execauto-clean semantics.
2.0.0
- Made guest execution fail closed by default; host compatibility execution now requires
explicit opt-in with
--allow-host-compatorallow_host_compat=True. - Switched the main CLI commands to human-readable output by default and kept
--jsonfor structured output. - Added default sizing of
1 vCPU / 1024 MiBacross the CLI, Python SDK, and MCP tools. - Unified environment cache resolution across
pyro,Pyro, andpyro doctor. - Kept the stable environment-first contract centered on
vm_run,pyro run, and curated OCI-published environments.
1.0.0
- Shipped the first stable public
pyroCLI,PyroSDK, and MCP server contract. - Replaced the old bundled-profile model with curated named environments.
- Switched distribution to a thin Python package plus official OCI environment artifacts.
- Published the initial official environment catalog on public Docker Hub.
- Added first-party environment pull, inspect, prune, and one-shot run flows.