Add style runtime compatibility guidance - #80637
MaggieCabrera wants to merge 2 commits into
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Hey @MaggieCabrera , I've just seen this PR 😅 Sorry! I'm thinking that this info could be actually more useful if added to And in that case, I'm not sure we'd need a dedicated Agents.md file to point at the README? Maybe we could use some eval, if available as a framework on this small change (cc @jeryj ) to A/B the usefulness of an agents.md file here? |
What?
Add package-scoped guidance that treats the shared style runtime registry as a backward-compatibility contract.
Why?
Gutenberg 23.1.1 introduced
@wordpress/style-runtimein #77965. During review, @ciampo identified the shape ofglobalThis.__wpStyleRuntimeas a compatibility boundary between separately bundled versions, while @mirka and @youknowriad worked through how old and new consumers can coexist.Discussion
This is a release-learning proposal, not a settled conclusion. Please challenge the evidence, scope, wording, or destination. Closing this PR is a useful outcome if the guidance is not durable or correct. Discussion here will be used to improve this skill.