How does the versioning of the sdk work and what are the guidelines to keep up with sdk version changes?

[opensourcegeek]

I'm not sure how this library is versioned, I was looking at an issue with different versions of sdk pulled in by 2 different libraries into a microservice, 2.20.39 and 2.21.46. I'm not sure why patch versions or minor versions have changes that completely changes or adds things to public API (eg). Pinning the version of sdk at root of a service fixes this issue, but still I didn't think minor versions will have breaking changes.

This gets even more frustrating when we need to work out whether localstack needs to be upgraded, and we have several services that share localstack config, so not all of them can be upgraded to the latest and greatest at the same time. Although they can be worked around, it usually takes some significant debugging time to find a localstack version that works for all of services without introducing more config changes for localstack. It took some time to figure out that I should switch to 2.20.59 to keep all services happy (https://stackoverflow.com/a/77476794/327702) without changing other services.

All of this is fine, but it took some doing to get there, so really, to keep up with your changes and possibly localstack's as well are there any good guidelines to follow? I think pinning the version of sdk at root of a service helps (which we weren't doing before), but even then localstack aren't always caught up with the changes. It would be really really useful if there's an aws sdk versions and compatible localstack versions maintained somewhere and also highlighted in the sdk docs.