[patch] Release v1.7.13

[kpango]

[patch] Release v1.7.13

Changelog

[Bugfix]

• General Fixes

  1. fix: add checkout option #2545 (#2546)
  2. fix: make format #2534 (#2540)
  3. fix conflict bug #2537
  4. Bugfix that caused an error when argument has 3 or more nil arguments #2517 (#2520)
  5. Bugfix recreate benchmark job when operator reboot #2463 (#2464)
  6. Fix agent-faiss build failed #2418 (#2419)
  7. Fix the logic to determine docker image #2410 (#2420)

• Backport and Release-Related

  1. Fix workflow trigger for backport pr creation #2471 (#2472)
  2. Fix output settings to determine-docker-image-tag action and release branch build tag name #2423 (#2425)

• E2E and Index

  1. Fix e2e for read replica and add e2e for index operator #2455 (#2459)
  2. Fix index job logic to pass DNS A record #2438 (#2448)

• Documentation and Other

  1. fix: typo of execution rule #2426 (#2427)
  2. 📝 Fix typo of file name #2413 (#2415)

[Enhancement]

• General Improvements

  1. Update dependencies, C++ standard, and improve Dockerfiles for better build systems and localization #2549 (#2557)
  2. Implement ngt Statistics API #2539 (#2547)
  3. refactor index manager service add index service API to expose index informations #2525 (#2532)

• API and Logic Changes

  1. Change default image tag from latest to nightly #2516 (#2518)
  2. update large top-K ratio handling logic #2509 (#2511)
  3. add inner product distance type for ngt #2454 (#2458)
  4. Implement index operator logic for read replica rotation #2444 (#2456)

• Performance and Optimization

  1. update deps & add validation for Flush API when agent is Read Only #2433 (#2436)
  2. Add index-operator template implementation #2375 (#2424)

• Testing and Metrics

  1. Implement client metrics interceptor for continuous benchmark job #2477 (#2480)
  2. Add tests for index information export #2412 (#2414)

[CI]

1. [create-pull-request] automated change #2552 (#2556)
2. Add workflow to check git conflict for backport PR #2548 (#2550)
3. [CI] Add workflow to synchronize ubuntu base image #2526 (#2527)
4. Automatically add backport main label for release-pr #2473 (#2475)

[Backport]

1. Backport PR Fix info path location #2542, Deleted unnecessary event path for docker build #2538 to release/v1.7 #2543
2. Backport docs updates to release/v1.7 #2521
3. Backport Flush API #2434

[Documentation]

1. capitalize faq #2512 (#2522)
2. add faiss in values.yaml & valdrelease.yaml #2514 (#2519)
3. add read replica and rotator docs #2497 (#2499)
4. Update continuous benchmark docs #2485 (#2486)
5. docs: add hrichiksite as a contributor for doc #2441 (#2442)

[Other]

1. Add base of benchmark operator dashboard #2430 (#2453)
2. Add client metrics panels for continuous benchmark job #2481 (#2483)
3. Add unit tests for index operator #2460 (#2461)
4. add reviewer guideline #2507 (#2508)
5. Sync release/v1.7 to main #2495
6. Add snapshot timestamp annotations to read replica agent #2428 (#2443)
7. Update build rule for nightly image #2421 (#2422)

Versions

• Vald Version: v1.7.12
• Go Version: v1.22.5
• Rust Version: v1.80.0
• Docker Version: v27.1.1
• Kubernetes Version: v1.30.3
• Helm Version: v3.15.3
• NGT Version: v2.2.4
• Faiss Version: v1.8.0

[coderabbitai]

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

100 files out of 256 files are above the max files limit of 50. Please upgrade to Pro plan to get higher limits.

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

---

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 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 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 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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

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.