After some internal discussion, we're not comfortable rushing this fix into 8.1.26 so late in the cycle because of the risk of further regression. It's been bumped to the 8.1.27 release.
After some internal discussion, we're not comfortable rushing this fix into 8.1.26 so late in the cycle because of the risk of further regression. It's been bumped to the 8.1.27 release.