Rolling back Plotly after a figure schema upgrade: what breaks when figure['version'] no longer matches
Plotly has stored a figure['version'] field in serialized figures since v5.3, and loading a figure written by a newer release can trigger compatibility checks or silently drop unknown trace attributes. I am planning an upgrade from Plotly 5.x to a newer 5.x/6.x line and need a rollback strategy for figures already saved with plotly.io.write_json . The constr
plotly