v0.1.4

What's Changed

• fix: gate SSH dispatch to Docker-capable workers by @kaiitunnz in #74
• chore: bump trl to 1.6.0 and adapt the worker training stack by @kaiitunnz in #75
• feat: extend capability gate to all task types by @kaiitunnz in #76
• feat: report component versions across server, worker, SDK, and CLI by @kaiitunnz in #78
• fix: prevent vllm_omni from breaking Qwen3 vLLM inference by @timzsu in #79
• fix: recover stuck workers when an MPExecutor subprocess dies by @kaiitunnz in #82
• perf: import worker executors lazily via a registry by @kaiitunnz in #83
• chore: bump version to v0.1.4 by @kaiitunnz in #80

Known Issues

v0.1.4 has an issue where the MPExecutor does not clean up the descendant processes of its own child process, leaving them orphaned, on non-ExecutionError exceptions. This is a breaking problem when the executor's child process holds GPU memory indefinitely. The problem has been fixed in v0.1.5-rc.1.

Full Changelog: v0.1.3...v0.1.4

FlowMesh container images for v0.1.4

Image	Platforms	Digest
ghcr.io/mlsys-io/flowmesh_server:v0.1.4	linux/amd64,linux/arm64	sha256:2995538223516290253767f32a11462530d3f8ec8dfefbf251f1fd9c4eca6ca1
ghcr.io/mlsys-io/flowmesh_worker:v0.1.4-cpu	linux/amd64,linux/arm64	sha256:d11c72dce1240469e02e69d730d7301b52af94617cc1e00871972f956551b88c
ghcr.io/mlsys-io/flowmesh_worker_builder:v0.1.4-gpu	linux/amd64,linux/arm64	sha256:18f2b9e2f248fb4e916bbd3c9f8335cc16283fb49e969110543c573b409c6233
ghcr.io/mlsys-io/flowmesh_worker:v0.1.4-gpu	linux/amd64,linux/arm64	sha256:88c8658043049982e6a0faef277d38723eb0eff0bf4e713b5dc38365e5038b94
ghcr.io/mlsys-io/flowmesh_ssh:v0.1.4-cpu	linux/amd64,linux/arm64	sha256:cd9943bd94e25744604b089a1d22ca7987d284c4ecdfd0b58b03e108ef1acf63
ghcr.io/mlsys-io/flowmesh_ssh:v0.1.4-gpu	linux/amd64,linux/arm64	sha256:d402933922c080e97bb91ebe222e41594e7080408b7bbbad922bf824dbdabdf4