[Question] Extension version not following semantic versioning patterns

[wsmelton]

Describe scenario

Reference #3827 it was found that in August 2023 Flux Extension 1.7.5 and 1.7.6 both got released that included BREAKING CHANGES!!! (Flux v2 v2.0.0/v2.0.1)

You released Flux v2 2.0.0 that had breaking changes where it broke cluster deployments because that version of Flux removed fields in kustomization kind.

Question
How can Microsoft team not following best practices and allow breaking changes in a minor version release of an extension?!!?

Why was that upgrade not released as 1.8.0 at least, or 2.0.0 version of the extension?

[wsmelton]

Can anyone on the team respond to this?

A breaking change for Flux Extension is coming according to the documentation. If this is released by minor and not major means a ton of AKS clusters are going to inherit this breaking change automatically.