Clarity on release versions, breaking changes, and runtime/architecture compatibility

[edjshelton]

Today I updated our log forwarders to the latest version only to find they immediately started erroring because the minimum required Python runtime version had changed from 3.13 to 3.14.

When the minimum required Python runtime version changes, it is absolutely necessary that the release containing the change is made a breaking change with a suitably obvious warning and explanation in the release notes.

This has caused problematic upgrades three times for us now (once when the architecture requirement changed to only arm64 and twice due to Python version changes).

Also, it's unclear how the RDS EM forwarder lambda versioning works - what is the latest version and can it have its own dedicated release please? There seems to be a lot of cross-contamination between the various lambdas in this repo and it's really confusing and problematic.

Thank you 🙏🏻

[edjshelton]

@klivan @RaphaelAllier sorry for the ping but would be good to get your thoughts on this 🙏🏻

[RaphaelAllier]

@edjshelton Sorry for missing this issue. We'll try to be more clear with the releases in the future, sorry about the troubles caused.

As far as the RDS enhanced monitoring function release is concerned, we usually release it by pushing a new version of that lambda on the AWS marketplace.
However I agree that the Github releases make that confusing. That specific lambda function doesn't see a lot of changes so usually copy/pasting the latest version of the code onto the lambda should do the work