[Andriciuc]

Description

Covers highlights from the 9.2 release including:

• Persistence and replication: forkless snapshots and full syncs, LZ4/Zstandard streaming compression, replication throttling
• Security: ACL roles with CLI examples, ACL DIGEST, secondary TLS certificate, OpenSSL-sourced randomness
• Availability under load: priority for system-critical events, reserved connections for administrators, cluster failover controls
• Performance: B+ tree sorted sets, batched lookups and prefetching, faster replication and cluster bus
• Efficiency: listpack for hashes with field expiration, shared client objects, script cache limit
• Observability: server-side hot key detection, transactions in the slow log, replication and cluster link metrics
• New data type and commands: Path Hash with CLI examples, INCREX, DELEX, conditional EXEC, XACKDEL/XDELEX
• Tooling: valkey-benchmark datasets and larger keyspaces, valkey-cli environment variables
• Before you upgrade: behavior changes to check for the user

Issues Resolved

Closes #676.

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 2

• content/blog/2026-11-15-valkey-9.2-release/index.md is excluded by !content/blog/**
• static/assets/media/featured/valkey-release-9-2.svg is excluded by !**/*.svg

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 63069723-8545-4c34-a221-a3fb64c54e61

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[madolson]

Overall I think most of the structure is OK. It would be nice to add some more narrative structure instead of just a list of features. I would rather talk about fewer features but explain in more detail why they are useful. Lots of aside comments like, "Along with info fields" which I don't think are necessary. When talking about performance, we should include headline numbers when they're relevant.

[stockholmux]

I'll withhold specific comments until the next revision.

1.) The blog is comprehensive, but I think that might be a weakness. It reads like expanded release notes, which is probably not the goal.
2.) It needs to be shorter. We don't need to give every detail. Let's look at the banner features/themes (what we wrote blogs about) and give a 1-3 paragraph description. Focus on why this is important and less of what the feature does.
3.) Anything that falls below the threshold of banner feature goes into a single heading - group these if possible.
4.) The intro needs to underline why this release is important.
5.) The confusion needs to give some more interesting CTAs. What's your favourite - post about that? Can you add these features change another open source project - make the changes, etc.

[Andriciuc]

@stockholmux thank you for the review! I went into this with a technical mindset and went gung-ho on the details. I took your points and rethought how this release brings value to our readers so I restructured the content:

• reworded the intro around the release's main benefit, getting more out of the hardware you already run, backed by the features and measurements merged in 9.2 (similar to the sorted set blog),
• restructured the content around the banner features, mostly the ones with their own blog posts, and I tried to keep the max 3 paragraph requirement: grouped commands into a single heading, shortened descriptions so we focus on the benefit of an added feature/command,
• grouped everything below that under a single "Also in this release" heading, and dropped details, keeping only the benefits for the reader (they can check the rn for details). All of those are from the previous subtopics like Availability under load, Performance, Security, Efficiency, Resource isolation, Observability, the command list and Tooling, all of which are trimmed/merged,
• I completely replaced the closing with your suggested CTAs.

I was thinking what to do with the "smaller" features, so I pulled them into the Also in this release subtopic, I think it saves the reader time to quickly skim over since they're already reading the blog but I can delete it if it feels like too much padding.

I do have a question though, is it ok since we have deep-dive posts for the banner features, to add the links to them once they're merged (and this one releases)?

[Andriciuc]

Rebased.

[greptile-apps]

Confidence Score: 4/5

[Low impact] The change reaches readers of the Valkey blog, not running Valkey deployments.

Hold merging until the post has draft = true, or until it is ready to publish immediately.

Findings

1.  Release announcement appears early ▶

Summary

Adds a featured Valkey 9.2 announcement covering:

• Readers can see how Valkey 9.2 saves data and handles heavy load.
• Readers can explore Valkey 9.2's new access and data commands.
• The announcement gathers Valkey 9.2's extra release details and upgrade notes.

The post needs draft = true to stay hidden until November 15.

_{Reviews (1) · Last reviewed commit: "Rewrite intro and clarify XACK/XDEL" · Reviewed by Greptile}