docs(valkey): release notes v2.0.0 - #17
Merged
Merged
Conversation
Add releaseNotes.queryTemplates mw-valkey-v2.0.0-fixed / -known (ECO, fixVersion-scoped, ReleaseNotesStatus = Publish) to doom.config.yml and the Fixed Issues / Known Issues directive sections under 2.0.0 in release_notes.mdx. The compatibility matrix and lifecycle row from #15 are unchanged; publish-loop validate_coupling passes for v2.0.0 with ACP v4.2, v4.3, v4.4.
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
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
Wire the v2.0.0 release-notes query templates into the docs build, so the
Jira-published notes for
Valkey-v2.0.0render on the release-notes page thesame way they do for the redis docs.
doom.config.yml: addreleaseNotes.queryTemplatesmw-valkey-v2.0.0-fixed/mw-valkey-v2.0.0-known(ECO project,fixVersion-scoped, gated on
ReleaseNotesStatus = Publish).docs/en/release_notes.mdx: add the### Fixed Issues/### Known Issuesdirective sections under 2.0.0, placed before "Before adopting 2.0.0".
No product claims were changed. The compatibility matrix (
v2.0.x→ Valkey7.2 / 8.1 / 9.1 → ACP v4.2, v4.3, v4.4) and the lifecycle row already merged in
#15 are the values the release confirmed.
Validation
yarn lint(doom lint): 0 errors, 0 warnings.validate_coupling.py(publish-loop): PASS for v2.0.0 against the ecoscantuple at the tagged tree (
3f853d16, server lines 7.2 / 8.1 / 9.1) and theoperator-confirmed ACP set
v4.2,v4.3,v4.4.fixVersion = Valkey-v2.0.0, so bothsections render empty until the first 2.0.x patch publishes notes.
docs/shared/crds/rds.valkey.buf.red_valkeys.yamlis generated(controller-gen) and was flagged, not edited — regenerate from the operator
source if it drifts.
Opened by publish-loop
pub-valkey-200-20260902(release-looprel-valkey-200-20260902, tagv2.0.0at3f853d16).🤖 Generated with Claude Code