Updates Redis to 6.2.10 #1937
Merged
Updates Redis to 6.2.10 #1937
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
BYK
approved these changes
Jan 26, 2023
chadwhitacre
approved these changes
Feb 13, 2023
There was a problem hiding this comment.
LGTM but what version are we on in SaaS prod for the record @hubertdeng123?
hubertdeng123
approved these changes
Feb 13, 2023
|
lol looks like we're on redis 5.0 here |
|
TIL image-mirror. Are we sure that's reflective of what's in SaaS? |
|
ok, let me confirm to be sure. Looks like redis 5.0 image is used for dev and I saw it being pulled in for getsentry tests |
|
Looks like depending on the cluster, we're running either 5.x of 6.x |
|
Sounds good. Ship it! 🚢 |
|
Thanks @danielhartnell! :-) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Redis patched two CVEs in release
6.2.9. We would like to update the Sentry container to apply those fixes:https://github.com/redis/redis/releases/tag/6.2.9
After that release, it looks like they pushed a bug fix in
6.2.10so it probably makes sense to bump up to that.If there's anything I can do to help test or evaluate this change, let me know.