Address direct dependency upgrades #3318
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The following changes will be applied to the production Kubernetes cluster upon merge. BE AWARE this may not reveal changes that have been manually applied to the cluster getting undone—applying manual changes to the cluster should be avoided. No manifest changes found for prod. |
SorenSpicknall
requested review from
charlie-costanzo
and removed request for
hunterowens
charlie-costanzo
approved these changes
Mar 28, 2024
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updates dependencies from the current automatic
chorePRs that are directly controlled via pyproject.toml files and requirements.txt files, ignoring those that are a layer deep inside automatically configured poetry.lock files. Also ignores the suggested upgrade to black 24.3.0 across the board, since there's a conflict with a black version required by another dependency in Poetry (to be investigated separately).Type of change
How has this been tested?
All changed Docker images and packages were built locally before merge
Post-merge follow-ups
Any refs to specific version numbers for these packages, services, and images will need to be updated. This cannot be done in this PR because those updates rely on publication of the changes from this PR (e.g. new image version and new package versions). This round of changes will include updates to two Kubernetes kustomization files.