Release versioning

[Bunzab]

Hi

I'd like to query your versioning decisions. We generally allow any new patch releases to be auto deployed via semantic versioning i.e.

    elasticstack = {
      source  = "elastic/elasticstack"
      version = "~>0.11.15"
    }

The last patch version 0.11.18 is pretty big and broke our CI. Easily fixed but should changes that include breaking changes be included in a patch version? By breaking changes I mean anything that requires a syntax change in our TF code. Not necessarily bugs but still enough to break test deploys. I'd expect this to be a new minor version and not a patch.

Thanks
Darrell

[tobio]

The last patch version 0.11.18 is pretty big and broke our CI

Firstly, apologies for the breakage here, it's annoying for you to have to deal with that and it's the last thing we want to force onto our practitioners.

I've updated the changelog in #1364 to include more details about the breaking change included here as well.

Ultimately you're right, this should never have been a patch version and was intended to be released as 0.12. We had some failures on our internal process which meant that these changes were released earlier than intended, and under the wrong version increment. We've fixed the process gap here, and ideally shouldn't see this happen again.