feat(victoria-metrics-operator): update helm chart version

[marcelaraujo]

Summary by CodeRabbit

• Chores
  • Updated the victoria-metrics-operator dependency to version 0.49.1.

[coderabbitai]

Walkthrough

The victoria-metrics-operator dependency version in the Helm chart definition was bumped from 0.44.0 to 0.49.1. No other modifications were made.

Changes

File(s)	Change Summary
charts/groundcover/Chart.yaml	Updated victoria-metrics-operator version from 0.44.0 to 0.49.1

---

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

🔭 Outside diff range comments (1)

charts/groundcover/Chart.yaml (1)

91-91: ⚠️ Potential issue

Bump this chart’s version for a release.
Whenever you update a dependency, the chart version must increment so Helm can detect and package the change.

- version: 1.9.378
+ version: 1.9.379

🧹 Nitpick comments (1)

charts/groundcover/Chart.yaml (1)

30-30:

Details

❓ Verification inconclusive

Verify the new dependency version is published.
Confirm that victoria-metrics-operator v0.49.1 actually exists in the Victoriametrics Helm chart repo before merging.

Don’t forget to run helm dependency update to refresh Chart.lock after bumping this dependency.

---

🏁 Script executed:

#!/bin/bash
# Check if version 0.49.1 is available in the Victoriametrics Helm charts repo
curl -s https://victoriametrics.github.io/helm-charts/index.yaml \
  | grep -A2 "name: victoria-metrics-operator" \
  | grep "version: 0.49.1"

Length of output: 136

---

Verify victoria-metrics-operator v0.49.1 is published
I ran the Helm‐charts index check and didn’t see version: 0.49.1 for victoria-metrics-operator. Please confirm it’s been released to https://victoriametrics.github.io/helm-charts before merging.
Don’t forget to run helm dependency update afterward to refresh Chart.lock.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dfb971a and a64e8a8.

📒 Files selected for processing (1)

• charts/groundcover/Chart.yaml (1 hunks)