Semver - breaking changes

[mimol91]

The new release 3.8.0 introduced breaking changes (see: formancehq/formance-sdk-go#57) For example, removing request.Request.RequestBody (that was not even marked as deprecated)

However, according to doc https://docs.formance.com/resources/release-policy It state that Formance follows sem-ver.
Breaking changes should be only in major releases.

Does it mean that API version can cause breaking changes even tho release is marked as minor?

[Quentin-David-24]

Hi @mimol91, thanks for raising this.

A recent speakeasy update introduced unintended changes to the API, most notably to RequestBody.
Version 3.8.1 restores the previous behavior and does not include those breaking changes.

Could you upgrade to 3.8.1 and confirm whether it resolves the issue?

You're right that breaking changes should increment the major version. This was an error on our end, and we apologize for the disruption.