Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A recent community contribution was aiming at removing the upper version pin on
botocore
(#8210, thanks @matt-mercer!). Unfortunately, the latest release at the time contained an invalid spec which was reported in boto/botocore#2925.The latest release of
botocore
now contains the requested fixes to the kafka service specs: boto/botocore@8bd1a4dThis is why we can finally remove the pin again.
In the future we might introduce an automate approach (using dependabot or similar bots) to explicitly upgrade these core libraries on a fixed schedule (to move more towards a proactive approach instead of the currently rather reactive approach when new releases of these libraries - like werkzeug or botocore - break our builds).
With #8307 we also moved
botocore
andboto3
from the install dependencies to the runtime extra (aka from a CLI dependency to a runtime dependency, which allows us to be more restrictive with the pins since the CLI dependencies have a wider impact compared to the runtime dependencies which are usually only used within our Docker images).