Update CI to Redis 8

[robert-oleynik]

Steps to test:

• CI should pass

Issues:

• upgrade Redis to latest major version

[coderabbitai]

📝 Walkthrough

Walkthrough

The Docker Compose configuration was updated to change the Redis service image from version 7.4 to 8. No other modifications were made to the service definition or its configuration.

Changes

File(s)	Change Summary
.github/docker-compose.yml	Updated Redis image tag from redis:7.4 to redis:8

Suggested labels

CI

Suggested reviewers

• normanrz

Poem

🐇
Compose files hop, a version swap,
Redis 8 now takes the top!
No ports or checks were made anew,
Just fresher carrots in the stew.
The service runs, the code is neat—
Docker bounces on its feet!

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/docker-compose.yml (1)

100-100: Consider pinning the Redis version for reproducible CI builds
Using the floating 8 tag could introduce unexpected behavior if a future patch release includes breaking changes. Pinning to a specific minor/patch version (e.g., redis:8.2.9) can help maintain stability in your CI environment.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66c1d68 and 8a2e7a8.

📒 Files selected for processing (1)

• .github/docker-compose.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build-smoketest-push
• GitHub Check: backend-tests

🔇 Additional comments (2)

.github/docker-compose.yml (2)

100-100: Upgrade Redis service image to major version 8
The image tag has been updated from redis:7.4 to redis:8, which aligns with the PR objective of moving CI to Redis 8.

---

100-100:

✅ Verification successful

Verify Redis 8 image availability on Docker Hub
Ensure the redis:8 tag exists and is accessible in your CI environment by running:

---

🏁 Script executed:

#!/usr/bin/env bash
# Skip cloning: only an external Docker Hub check
curl -s https://registry.hub.docker.com/v2/repositories/library/redis/tags/8 | jq '.name'

Length of output: 93

---

Redis:8 image tag confirmed on Docker Hub
The redis:8 tag exists and is accessible (verified via the Docker Hub API), so no further changes are required.