chore(deps): update dependency @algolia/client-search to v5.20.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@algolia/client-search (source)	5.19.0 -> 5.20.4

---

Release Notes

algolia/algoliasearch-client-javascript (@​algolia/client-search)

v5.20.4

Compare Source

• 92bd911848 chore(scripts): point jira issues to another epic (#​4505) by @​millotp
• b8918494d0 chore(deps): dependencies 2025-03-03 (#​4511) by @​algolia-bot
• 97d2722bc9 fix(specs): Increase optionalWords visibility in docs (#​4559) by @​gazconroy

v5.20.3

Compare Source

• ecd6bc4fed chore(deps): dependencies 2025-02-17 (#​4459) by @​algolia-bot

v5.20.2

Compare Source

• c0e70d9864 chore(deps): dependencies 2025-02-10 (#​4432) by @​algolia-bot

v5.20.1

Compare Source

• 506b8a5636 fix(specs): responseFields description (#​4399) by @​kai687
• 09e657fa76 fix(specs): add a linter to assert that type is present (#​4393) by @​millotp
• 27ad6df2ab chore(deps): dependencies 2025-01-27 (#​4395) by @​algolia-bot

v5.20.0

Compare Source

• 5aa57630d6 feat(specs): only use shortname in the source input (#​4287) by @​millotp
• 1e847f4caf fix(specs): move customRanking and keepDiacriticsOnCharacters to indexSettings (#​4324) by @​millotp
• 13742383ab chore(deps): dependencies 2025-01-13 (#​4325) by @​algolia-bot
• 58cc5449f5 fix(specs): optionalFilters additional explanation (#​4353) by @​kai687
• 3b129e01df fix(specs): ingestion expected and received events type (#​4356) by @​shortcuts
• 22167b8e68 fix(specs): extend Analytics descriptions (#​4360) by @​gazconroy
• 5b14906c1e fix(specs): remove the processing outcome (#​4359) by @​millotp
• 952639f0fb fix(specs): adjust style for banner descriptions (#​4362) by @​kai687
• 4ae9ccd89f chore(deps): dependencies 2025-01-20 (#​4365) by @​algolia-bot
• 83f188d333 feat(specs): rename composition to composition-full (private) and add composition (public) (#​4357) by @​e-krebs
• e842e63d4e fix(javascript): use beta version (#​4385) by @​shortcuts

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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.
  • Generate unit testing code 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 testing code 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 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 generate unit testing code.
  • @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.

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