RS: Remove the OpenSSL 3.3 requirement from the 8.2.0 release notes - #3789
Merged
Conversation
The 8.2.0 line never required OpenSSL 3.3. The RED-196656 fix (RS built against an earlier OpenSSL, rather than adding a pre-upgrade check) was already present in v8.2.0-25, the first 8.2.0 GA build, so no shipped 8.2.0 version was ever affected. Confirmed two ways: - Mariana Aviv on RED-196656: "this fix is part of the 8.2.0-25 build BUT is not yet part of 8.0.20 (this will only come on the next branch maint.)" - Build tags in Redis-Enterprise: v8.2.0-25 (2026-07-17) and v8.2.0-46 (2026-08-03) both contain fix commit ed048dbc6b (2026-07-12). v8.0.20-68 does not contain it; v8.0.20-96 does. Until now the pages told 8.2.0 users to run `openssl version` and upgrade openssl/openssl-libs before upgrading -- unnecessary work that never applied to their version. This partially reverts #3762 (DOC-6946) for the 8.2.0 line only. That change correctly scoped the requirement to RHEL 9, but propagated it onto the 8.2.0 pages where it did not apply. The 8.0.x pages keep the requirement, because it genuinely applies to 8.0.16 through 8.0.20-68. Found while drafting the 8.0.20-96 notes: the inherited "Version changes" section contradicted the release's own resolved-issues list, which includes RED-210040, the 8.0.20 cherry-pick of the same fix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at 48f8804 |
Contributor
dwdougherty
approved these changes
Aug 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Removes the OpenSSL 3.3 requirement from the 8.2.0 release notes. The 8.2.0 line never required it.
Three files, pure deletions (36 lines, nothing added):
rs-8-2-0-25.mdrs-8-2-0-46.md### OpenSSL versionblockrs-8-2-releases/_index.mdWhy
The RED-196656 fix — RS built against an earlier OpenSSL, rather than adding a pre-upgrade check — was already in
v8.2.0-25, the first 8.2.0 GA build. So no shipped 8.2.0 version was ever affected.Confirmed two independent ways:
Redis-Enterprise:v8.2.0-25(2026-07-17) andv8.2.0-46(2026-08-03) both contain fix commited048dbc6b(2026-07-12).v8.0.20-68does not;v8.0.20-96does.Customer impact: 8.2.0 users were being told to run
openssl versionand upgradeopenssl/openssl-libsbefore upgrading — unnecessary work that never applied to their version.Relationship to #3762
This partially reverts #3762 (DOC-6946) for the 8.2.0 line only. That change correctly scoped the requirement to RHEL 9, but propagated it onto the 8.2.0 pages where it didn't apply.
The 8.0.x pages deliberately keep the requirement — it genuinely applies to 8.0.16 through 8.0.20-68. The matching 8.0 correction (scoping it to that range, since -96 lifts it) is in #3787 and is gated on the -96 GA, because it references a build that hasn't shipped yet. This PR has no such gate: the 8.2.0 pages are wrong now, so it can merge immediately.
Notes for reviewers
main(130/130, 123/123, 62/62) — deletions only, so nothing new introduced and nothing masked.rs-8-2-0-25.mdandrs-8-2-0-46.md. Whichever merges second may need a trivial conflict resolution — keep the JWT section, drop the OpenSSL one. Merging RS: Document JWT token invalidation on upgrade to 8.0.22 and later #3779 first is smoother since it's already approved.No DOC ticket yet — this was found during release-note drafting rather than reported.
🤖 Generated with Claude Code
Note
Low Risk
Pure documentation deletions with no product or runtime behavior changes; only corrects misleading upgrade guidance for 8.2.0 readers.
Overview
Removes OpenSSL 3.3 on RHEL 9 upgrade guidance from Redis Software 8.2.x release documentation, because that requirement never applied to the 8.2.0 line (the RED-196656 build fix was already in the first GA builds).
The OpenSSL version on RHEL 9 section is deleted from the 8.2.x index and from
rs-8-2-0-25.md; the shorter OpenSSL version block is removed fromrs-8-2-0-46.md. Version changes now goes straight from breaking changes (where present) to Reserved ports.8.0.x release notes are unchanged and still document the OpenSSL requirement where it applies.
Reviewed by Cursor Bugbot for commit 48f8804. Bugbot is set up for automated code reviews on this repo. Configure here.