If there are breaking changes in a Dagster release why is only the patch version incremented? https://docs.dagster.io/changelog#107

• The constructors to

InputMapping

and

OutputMapping

were not public APIs (e.g. see https://docs.dagster.io/1.0.6/_apidocs/graphs#dagster.OutputMapping). We could have been more clear about this in the changelog. • The Dagit change removes some redundant functionality in the UI, but doesn't break anything. We probably should have categorized it differently. fyi @chris

Thanks for the explanation, was just bit by AWS DMS having breaking changes in the patch version so it’s on my mind