WPTaverm
Interactivity API Gets a Formal Versioning Policy

news

Interactivity API Gets a Formal Versioning Policy

Store names, directive stability, and what you can break in a minor. The docs now say it in a voice that is not a hallway conversation.

by Riley Cho·August 12, 2026·0 Comments

The Interactivity API grew faster than its promises. A versioning note now spells out which directives are load-bearing and which are experiments wearing a stable-looking name.

Theme authors who bound a store to a class name they invented in 2024 should read the deprecation list before the next major. This is how you keep a client-side layer from becoming another undocumented runtime.

0 thoughts on “Interactivity API Gets a Formal Versioning Policy

    Leave a Reply

    Trending now