airbyte-ci: Update pipelines requests and pyjwt #36607
Merged
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.
What
This PR updates
requests
in pipelines to2.31
, andpyjwt
to the newest version (2.8.0)common_utils
. This makes sure thatpipelines
will get latestcryptography 42.0.5
, which solves severalk high severity security alerts.Why
It's easier to resolve requests and airbyte-ci pieces separately from the rest of connectors (see #36595) and test just the airbyte-ci in this PR.
Once that is done, not only this fixes 8+ security alerts, but also scope for #36595 is smaller and hence easier to push through.
Risks
Requests 2.29 and 2.30 was known to not work well with
docker
beforedocker 7.0
. I took care to update docker as well, and the internets tell me that this combo should work, but I'm not entirely sure — we should validate it.In #35910, the CI was failing yesterday with the following error:
This PR should also fix that problem.