Skip to content

Add release notes entry for Valkey 9.1.0 GA#3635

Closed
ranshid wants to merge 3 commits into
valkey-io:9.1from
ranshid:release-notes-9.1.0-ga
Closed

Add release notes entry for Valkey 9.1.0 GA#3635
ranshid wants to merge 3 commits into
valkey-io:9.1from
ranshid:release-notes-9.1.0-ga

Conversation

@ranshid
Copy link
Copy Markdown
Member

@ranshid ranshid commented May 5, 2026

Add a release notes entry for Valkey 9.1.0 GA covering the three security fixes being ported to the 9.1 branch:

  • CVE-2026-23479 — Use-After-Free in unblock client flow
  • CVE-2026-25243 — Invalid Memory Access in RESTORE command
  • CVE-2026-23631 — Use-after-free when full sync occurs during a yielding Lua/function execution

Only modifies 00-RELEASENOTES. The actual code fixes are in separate PRs targeting 9.1.

@roshkhatri
Copy link
Copy Markdown
Member

Is this supposed to be Valkey 9.1.0 GA?

@ranshid
Copy link
Copy Markdown
Member Author

ranshid commented May 5, 2026

Is this supposed to be Valkey 9.1.0 GA?

What else?

@roshkhatri
Copy link
Copy Markdown
Member

Is this supposed to be Valkey 9.1.0 GA?

What else?

RC3 for CVE?

@ranshid
Copy link
Copy Markdown
Member Author

ranshid commented May 6, 2026

Is this supposed to be Valkey 9.1.0 GA?

What else?

RC3 for CVE?

I do not think we will do an RC-3. this will just be part of the GA release

@ranshid ranshid marked this pull request as ready for review May 6, 2026 05:44
@zuiderkwast
Copy link
Copy Markdown
Contributor

There are lots of PRs in the "To be backported" column in the 9.1 project. They should be cherry-picked to the 9.1 branch and included in 9.1.0 too.

Also some still under review that I think we can merge before the release.

…-25243, CVE-2026-23631)

Signed-off-by: Ran Shidlansik <ranshid@amazon.com>
@ranshid ranshid force-pushed the release-notes-9.1.0-ga branch from 7d7242f to ced6804 Compare May 7, 2026 05:02
@ranshid
Copy link
Copy Markdown
Member Author

ranshid commented May 7, 2026

There are lots of PRs in the "To be backported" column in the 9.1 project. They should be cherry-picked to the 9.1 branch and included in 9.1.0 too.

Also some still under review that I think we can merge before the release.

@zuiderkwast - agree. I was not planning to start the ga release, mainly wanted to backport the CVE fixes at this point

@ranshid ranshid requested a review from madolson May 10, 2026 11:08
@zuiderkwast
Copy link
Copy Markdown
Contributor

Shall we keep this PR open and add more release notes to it while we backport more PRs?

@madolson
Copy link
Copy Markdown
Member

Yeah, @lucasyonge fyi, you should have permissions to update this with the remaining release notes.

@ranshid ranshid requested a review from lucasyonge May 12, 2026 04:57
@ranshid
Copy link
Copy Markdown
Member Author

ranshid commented May 12, 2026

I think in the long term - we should add a release section every time we : splt a new releaes branch and/or release rc candidate. maybe we can add this to the release process doc?( @madolson )

Updated release notes for Valkey 9.1.0, detailing new features, bug fixes, and contributor acknowledgments.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 12, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 056781c2-cedc-4f87-9e2a-e14d2308fdf4

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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Member

@enjoy-binbin enjoy-binbin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's also update the version together, see #3682

@lucasyonge
Copy link
Copy Markdown
Contributor

Let's also update the version together, see #3682

Let me close this and add GA section in PR #3682

@lucasyonge
Copy link
Copy Markdown
Contributor

Close this PR and add updated information in pr #3682 @ranshid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

6 participants