Skip to content

Releasing a new Valkey version

Roshan Khatri edited this page Sep 4, 2024 · 8 revisions

Major/minor release

TBD

New patch release

  1. Merge all commits from the corresponding project. Example 7.2.

  2. Submit a new PR that updates the version.h file along with updating the release notes.

  3. Cut a release here: https://github.com/valkey-io/valkey/releases/new. It should be based off of the target branch, e.g. "7.2", and the tag "7.2.5".

  4. Once the new version is released, this should trigger the workflow to build binaries (example workflow) and upload them to the S3 bucket. (This automation has not been merged in 7.2 branch yet, so one of the Maintainers will have to trigger it manually).

  5. To update the download links on the website with the new binaries. Please publish a PR like this to the website repository - https://github.com/valkey-io/valkey-io.github.io

  6. Update the valkey-hashes repository with the new release hash - https://github.com/valkey-io/valkey-hashes. To compute the SHA-256 hash, run the following command for the respective release version and submit a PR like this.

    VERSION=8.0.0-rc2;
    curl -LO https://github.com/valkey-io/valkey/archive/refs/tags/$VERSION.tar.gz && shasum -a 256 "$(basename https://github.com/valkey-io/valkey/archive/refs/tags/$VERSION.tar.gz)"
  7. Update the valkey-container repository - How to build and publish new version Docker Image

Clone this wiki locally