partial autorange gets overridden on subsequent `react` calls

I'm encountering some unexpected behavior pertaining to the partial autorange changes added in v2.26, which lets users use autorange behavior for one axis bound, but use a hard bound for the other.

After spending time on a minimal reproduction, distilled the core problem to autorange and range properties on layout.yaxis being overridden on subsequent calls to Plotly.react. For added context, I'm using react-plotly, which seems to exacerbate the problem (because Plotly relies on mutating the props supplied), but I'll remove React from the equation int his report and just focus on the raw Plotly behavior.

See the codepen here:
https://codepen.io/billy-littlefield/pen/JjqyXgW

In this example, I have a simple bar graph where the largest bar has value 4. In my layout, I set

• autorange: "min"
• range: [null, 50]

with the intention of forcing the top bound to be 50.

The "rerender" button in the top-left will call Plotly.react with the same arguments as the initial call. You can reset the demo using a button in the top right.

My expectation is that subsequent clicks to "rerender" would result in an identical graph. The observed behavior is that on initial render, the graph I see shows the expected partial autorange, but a subsequent render changes autorange to true and range to the calculated autorange. I can double click the graph to return to the initial layout settings, but I'm surprised that it changes on me in the first place.

If this is working as expected, please disregard. I understand that Plotly mutates layout (and potentially data) in the computation cycle, but figured these mutations would not override the original expressed intention of a graph layout. Seeing as the partial autorange behavior is relatively new, I wondered if this might be unexpected behavior.

Start with the linked CodePen and the raw Plotly.react calls, focusing on how layout.yaxis autorange and range are handled across repeated renders. Trace the update path that changes the partial autorange settings, then verify that repeated calls preserve autorange: "min" and range: [null, 50] and produce an identical graph.