chore(deps): update helm release redis to v18.12.0

[renovate]

This PR contains the following updates:

Package	Update	Change
redis (source)	minor	18.9.0 -> 18.12.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	df5a4d2
Status:	✅  Deploy successful!
Preview URL:	https://d91f076d.automation-app-bot.pages.dev
Branch Preview URL:	https://renovate-redis-18-x.automation-app-bot.pages.dev

View logs

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[semanticdiff-com]

Review changes with SemanticDiff.

[pr-code-reviewer]

👋 Hi there!

The most important things to improve in the code-diff are:

1. Update the version of the Redis dependency in both Chart.lock and Chart.yaml files from 18.9.0 to 18.12.0.
2. Update the digest of the Redis dependency in Chart.lock file from sha256:6f227a8f3daf48813df5576db57fd9a66062fe9d1213eb4a3d7a8e39c797be20 to sha256:e92bde97b8560d361851e4dee5e177ead373d66383d61a290c26b3cbd3d41d71.
3. Update the generated timestamp in Chart.lock file from "2024-01-26T13:47:14.788448009Z" to "2024-02-01T13:14:53.250258152Z".

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit-tests for this file.
• 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 generate unit tests for this file.
  • @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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[instapr]

Nice work updating the redis package to v18.9.1! The changes in the Chart.lock and Chart.yaml files look good.

No further action is needed.

[pr-explainer-bot]

Pull Request Report

Greetings! 👋

Here's a summary of the changes made in the pull request:

Changes

1. Updated the version of redis dependency in Chart.lock:

   • From: 18.9.0
   • To: 18.9.1
   • View changes in Chart.lock

2. Updated the version of redis dependency in Chart.yaml:

   • From: 18.9.0
   • To: 18.9.1
   • View changes in Chart.yaml

Suggestions

No suggestions for improvement were provided.

Bugs

No potential bugs were found.

Improvements

No specific improvements were suggested.

Rating

The code has been rated based on the following criteria:

• Readability: 8/10
• Performance: 9/10
• Security: 9/10

That's all for now! 🤖

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[mergeable]

⚠️

Please add Jira ticket id i.e. "JIRA-ID"

Check Fail Adhere to the branch naming convention described here