This is a Proof of Concept design to automate the process of release a new version for valkey. We can use a centralize repository to automate the process of build the binary files -> commit the new hash -> update the docker description
Currently we still don't have a unified process to automate the workflow. These are the steps still happen manually:
- Updating the valkey-hashes repository.
- Running a update script on valkey-container and committing the changes which triggers containers workflow to upload the images.
- Updating the website downloads page with the new releases.
Originally posted by @roshkhatri in #1396 (comment)
Below is the diagram of the current process:
To automated this process, we would create a centralized repository to take care of all these processes.
-
Create a
valkey-automation-botrepo that will be triggered when the mainvalkeyrepo release a new version. -
In this
valkey-automation-botrepo, the workflow will run the following steps:build the binary files->Open a PR for valkey-hashes->Open a PR for valkey-container. -
We can remove the
build-release-packages.yml,call-build-linux-arm-packages.yml,call-build-linux-x86-packages.ymlfromvalkeyrepo.
We need the PAT token that can give access to create a PR for
valkey-containerrepo andvalkey-hashesrepo.
Below is the flow diagram of the design:
Github action jobs
PR for valkey-hashes
PR for Docker Update
