Hi all, we might have caused a bit of trouble with the major release.
^
Based on this, we have always followed a cycle of major releases when a breaking change is fixed or a dependency update is addressed. In this case, it was both.
Having received feedback from the Steering Committee Members, and the team being on a clock to make it to the downstream EE build. We had to make a decision. Whether to make a major release or a minor one. But given the regression that was handled, we decided that a major release makes the most sense for us. We are open to updating our practices with any updated policies present.
As per the releases that happened, none of them consider any breaking change from a user standpoint.
Regards.