Versions
The artifact hash is the pinned version. A host registers the hash of the code it is running. Discovery offers an execution only to a host with that hash and a compatible handler digest.
A host running a different artifact does not receive the execution. The host log can say waiting-for-version when it can see the mismatch. The dashboard does not decide that. It shows the hash from the projection.
Deleting the version does not move the execution onto another artifact. The execution stays waiting for a process that still has the pinned hash.
There is no continuation migration from one program version to another.
Compatibility
Section titled “Compatibility”Pulse v1.0.0 is the published release.
| Component | Pulse v1.0.0 |
|---|---|
| Host | 1.0.0 |
| Host protocol | 1 |
| Node.js adapter | Node 22 and 24 |
| Linux architectures | AMD64 and ARM64 |
| Maximum serialized continuation | 16 MiB |
| Program-version continuation migration | Not supported |
| Python / Rust Pulse adapters | Not supported |
A continuation stays on the artifact hash it started with. Keep a process that still runs that artifact while those executions are active. A host whose artifact hash differs does not claim them.
Deploying a new application version
Section titled “Deploying a new application version”Ship the new artifact as a new deployment. Leave a host and adapter that still run the previous artifact until every execution pinned to that hash has finished.
A replacement that only has the new hash will not claim the older executions. Those executions wait. They do not move forward on the new code, and they do not fail over to it.