Compatibility

Which Pulse app versions can upload to which PulseVault servers. Generated from the upload-protocol versions each release declares — nothing here is edited by hand.

App and server versions

A Pulse app and a PulseVault server work together when the protocol versions they speak overlap. Open About in the app to see your version and whether each server you've paired with is compatible.

Pulse app ↓ · PulseVault →nextprotocol 2 · pinned dd89150, not released yet0.5.0protocol 20.4.0 – 0.4.2protocol 20.0.1 – 0.3.0protocol 1
2.2.3protocol 1–2✓ protocol 2✓ protocol 2✓ protocol 2✓ protocol 1
2.2.2protocol 1–2✓ protocol 2✓ protocol 2✓ protocol 2✓ protocol 1
2.2.1protocol 1–2✓ protocol 2✓ protocol 2✓ protocol 2✓ protocol 1
2.2.0protocol 1–2✓ protocol 2✓ protocol 2✓ protocol 2✓ protocol 1
2.1.0protocol 1–2✓ protocol 2✓ protocol 2✓ protocol 2✓ protocol 1
2.0.x and earlierprotocol 1✗ Update Pulse✗ Update Pulse✗ Update Pulse✓ protocol 1

Upload protocol versions

VersionWhat changed
1.0First version. /capabilities and pairing links carried uploadUnit (segment or merged).
2.0Breaking: uploadUnit removed from /capabilities and pairing links — a pulse always uploads as one video (§8). Clients built for 1.0 required it.
2.1Added protocolRevision to /capabilities, the Pulse-Client header with 426 Upgrade Required (§7.2), and Upload-Metadata.appVersion (§4.1).
2.2Added read-only view links: viewLinks in /capabilities, POST {prefix}/artifacts/<id>/view-link (§6.4), and the view token's use claim (§5.5).
2.3Added GET {prefix}/artifacts/<id>/status and GET {prefix}/artifacts/<id>/poster (§6.5), the capability token's ctx claim (§5.4), and the pulse-shape rule for creates (§5.4).

A change to the major version breaks compatibility with older apps or servers; a minor version only adds things older ones can ignore.

Protocol reference

Generated 2026-10-08 from mieweb/pulse and @mieweb/pulsevault dd89150.