Protocol changelog
The wire protocol evolves by addition. A new host may add methods, notifications, error kinds and optional fields at any time, and a client written against an earlier version keeps working: that is the guarantee, and it is why a schema fingerprint your client does not recognise is a warning rather than an error.
This page is the exception list — the surfaces that have changed in a way addition alone does not cover. It is generated from the record every such change has to be entered in before it can reach the schema, so a change missing here is a change that did not happen.
Non-additive changes
Section titled “Non-additive changes”These surfaces have changed beyond addition. Read the current definition of each before you rely on the shape you remember; everything not listed here has only ever gained members.
SessionDeleteCompletedParamsSessionDeleteFailureReasonSessionDeleteOutcomeSessionDeleteParamsSessionDeletePhysicalChange-32603session/deletesession/deleteCompleted
Deprecations
Section titled “Deprecations”None. The protocol is before its 1.0 release, and no removal window is owed while it is: a surface can change without first being announced as deprecated. From 1.0 onward a surface is removed only after it has shipped a deprecation notice in an earlier release, and each completed removal is listed here.