chore(ci): update boto3 library version to 1.26.164+

[leandrodamascena]

Issue number: #3631

Summary

Changes

We need to bump the boto3 library to 1.26.164+ to support the new ReturnValuesOnConditionCheckFailure feature for DynamoDB

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[rubenfonseca]

Question: what happens if people depend on the boto3 that comes with the runtime? Currently: boto3-1.26.90

[rubenfonseca]

Answering my own question: this is only for development and for layer customers

[allanlewis]

@rubenfonseca @leandrodamascena This is a problem for my project. I want to exclude boto3 and botocore from my deployment package because they take up a lot of space, but if I depend on this package with the boto3 extra then I can't have the runtime version of boto3, 1.26.90 as you correctly state, as a dev dependency alongside.

If it's the case that this package absolutely won't work with older versions of boto3 then how does it work in the Lambda environment (for Python 3.9 and 3.10 at least) at all?