Versioning

Every RCP envelope carries a version field. The current and only version ever shipped is:

"version": "1.0.0-alpha"

What “alpha” means here

RCP 1.0.0-alpha is a real, running protocol — it is what powers Replay and Billing in Runtime today — but the event taxonomy is still growing. New event types (file, tool, git, test and build events) are defined in the schema ahead of having a producer, which is why the version stays pre-release until that surface stabilizes.

Compatibility policy

• Adding a new event typeis not a breaking change — consumers should ignore event types they don't recognize.
• Adding an optional field to an existing payload is not a breaking change.
• Removing or renaming an existing field, or changing a field's type, is a breaking change and will bump the version.

Don't confuse protocol and CLI versions

The Runtime CLI has its own release version, independent of the RCP protocol version carried in each event. A CLI upgrade does not necessarily mean a protocol version change, and vice versa.

See Schema reference for the exact fields this version covers.