bump hiredis v1.2.0

[shogo82148]

Summary by CodeRabbit

• Chores
  • Updated the hiredis dependency to the latest version.

[coderabbitai]

Walkthrough

This modification updates the commit hash for the hiredis subproject within the dependencies (deps) directory. It's a straightforward change that ensures the project aligns with the latest or a specific stable version of hiredis, which is a minimalistic C client library for the Redis database.

Changes

Files Changed	Summary
deps/hiredis/...	Updated subproject commit hash

Poem

"In the garden of code, under the moon's glow,
A little rabbit hopped, updating as it goes.
With a swift change of hash, in hiredis's abode,
It whispered to the data, 'Let the newest tales be told.'
🌟🐰✨
So here's to changes, both big and small,
May they bring improvement, joy, and growth to all."

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.
  • 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 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 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.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between cf84beb and 1f2be12.

Files selected for processing (1)

• deps/hiredis (1 hunks)

Additional comments: 1

deps/hiredis (1)

• 1-1: The update to the subproject commit hash for hiredis to 60e5075d4ac77424809f855ba3e398df7aacefe8 aligns with the PR's objective of upgrading hiredis to version 1.2.0. This change is straightforward and appears correct based on the PR's description.

However, it's crucial to ensure that this update does not introduce any compatibility issues or breaking changes within the project. I recommend the following verification steps:

• Ensure that the project builds successfully with the updated hiredis version.
• Run existing tests to verify that the update does not break any functionality.
• Review the hiredis 1.2.0 release notes for any changes that might require adjustments in the project's use of hiredis.