RS: 7.22.2-179 - #3822
Merged
Merged
Conversation
Maintenance release note for RS 7.22.2-179 (Yellow Submarine maint 12, released 2026-08-14). Near-empty by design: all 11 fixVersion candidates were resolved through Cloners and none is itemizable — ten are Security, of which nine are dependency-CVE bumps in bundled Go/Node/Python binaries, and RED-210861 drops off entirely as Closed/Invalid. The one that matters is RED-210242. It reads as a routine cherry-pick titled "CP rediscore vulnerabilities" and nothing in the fixVersion query marks it, but it is the 7.22.2 clone of the embargoed Nexus open-source-Redis batch — provable here because it carries Blocks links to ten VDP tickets, none of which is in a released state. Its entries are deliberately absent and the Security section is the unchanged -170 carry-forward. The 7.8.6 sibling RED-210243 hides the same batch without the VDP links, so summary text alone will not reveal it next time. Three -170-specific blocks were stripped rather than carried forward: the UNWATCH proxy Enhancement, the RS188659 and RS159953 Resolved issues, and the matching Highlights bullets. Copying a maintenance template forward silently reasserts the previous build's fixes as if they shipped again. Learned: a Closed/Done cherry-pick in a maintenance candidate list can be embargoed content with nothing in Jira to flag it Constraint: never write RED-210242 or RED-210243 entries into a release note until the Nexus embargo lifts Constraint: strip Enhancements and Resolved issues when copying a maintenance RN template forward Rejected: appending a fixed-in note to RS153589 per this ticket's own instruction | RED-153589 is Closed/Outdated with no fixVersion, so it would publish a false claim - see DOC-6943 Directive: check the inherited Version changes section against this line's own resolved-issues list before trusting it Gaps: compatibleOSSVersion patch numbers are carried forward from -170, not sourced - the tag manifest confirms only the 7.4, 7.2 and 6.2 minor lines Ticket: DOC-6932 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
RS153589 ("the metrics stream engine preview reports incorrect latency metrics")
is deleted from the 7.22 line index rather than annotated as fixed. RED-153589 is
Closed with resolution Outdated, carries no fixVersion, and was abandoned as a
stale Cloud-origin report — so the rubric's fixed-known-issue treatment does not
apply, and appending a fixed-in note would publish a claim that is not true.
Follow-on to DOC-6847, which removed the same line from the 7.22.2-170 build page.
The 12 historical 7.22 build pages keep the entry by decision: they are snapshots
of what was known at that build, and only the line index reads as current state.
Learned: an Outdated resolution is Jira's abandoned-stale marker and not a fix, so it earns removal rather than a fixed-in note
Constraint: do not re-add RS153589 and do not annotate it as fixed if it resurfaces
Directive: DOC-6932's ticket body still instructs the opposite (keep the line, append a fixed-in note) and should be corrected
Ticket: DOC-6943
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Contributor
🧠 Redis MemoryFound 12 related items from repository history (2 new this commit):
Memory updated at de55549 |
7.22.2-179 follows 7.22.2-133, the build listed as carrying these fixes, so it inherits them in the cumulative security lists. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Merged
RED-210242 records the 7.22.2 cherry-pick under fix version 7.22.2_Aug26_SW_maint, described as "7.22.2-179. Nexus fix", so this build carries the whole Nexus batch. Entries go in every maintained Redis version section, per the backport tickets listing 7.4, 7.2, and 6.2 as targets. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Merged
7.22.2-179 bundles Redis 7.4, 7.2, and 6.2. Yaacov confirmed the vector set fixes apply from Redis 8.2 and tls-auth-clients-user CN from 8.6, so none of the three belong in this release note. The four core Nexus entries, the stream consumer group entry, and both Melissa entries remain. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Includes the Melissa and Nexus security entries for 7.22.2-179 (DOC-6970). Vector set and TLS CN entries are omitted: they require Redis 8.2+ / 8.6+.
Note
Low Risk
Documentation-only Hugo content with no product or runtime code changes.
Overview
Adds documentation for the 7.22.2-179 (August 2026) Redis Software maintenance build, including package SHA256 checksums for Ubuntu 20/22, RHEL 8/9, and Amazon Linux 2, plus the usual module/feature-set, platform, known-issue, limitation, and open-source security/CVE sections.
Updates the 7.22.x release-notes index by removing known issue RS153589 (metrics stream engine preview incorrect latency metrics) from the series-level list; the new build page lists only RS131972 and RS155734 as known issues (it also does not repeat RS156391 from the index).
Reviewed by Cursor Bugbot for commit de55549. Bugbot is set up for automated code reviews on this repo. Configure here.