VirtualMetric Director 2.0.5

[yusufozturk]

Summary by CodeRabbit

• Chores
  • Updated VirtualMetric DataStream image to version 2.0.5 from version 2.0.3.

[coderabbitai]

Walkthrough

The vmetric subject version is bumped from 2.0.3 to 2.0.5 in two places: the exported Registry map in internal/config/subject.go and the corresponding row in the README.md Subjects table.

Changes

VirtualMetric DataStream version bump

Layer / File(s)	Summary
vmetric version bump in config and docs internal/config/subject.go, README.md	The Version field in the Registry map's vmetric entry and the README Subjects table are both updated from 2.0.3 to 2.0.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• VirtualMetric/PipeBench#15: Previously bumped the same vmetric subject Version field and README entry to 2.0.3, making it the direct predecessor of this version bump to 2.0.5.

Poem

🐇 Hippity-hop, a version leaps ahead,
From 2.0.3 to 2.0.5 instead!
Two tiny lines changed, both neat and bright,
The Registry and README now set just right.
This bunny approves — what a delightful night! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'VirtualMetric Director 2.0.5' refers to a version bump but does not clearly summarize the actual changes made in the pull request, which are updates to README.md and subject.go to bump VirtualMetric DataStream image version from 2.0.3 to 2.0.5.	Revise the title to be more specific about the actual changes, such as 'Bump VirtualMetric DataStream image version to 2.0.5' or 'Update VirtualMetric DataStream version references to 2.0.5'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev-2.0.5-vm

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@internal/config/subject.go`:
- Line 200: The Version field in subject.go is being set to "2.0.5" which
references a non-existent Docker image vmetric/director:2.0.5. Verify the
correct Docker image namespace and tag (the namespace is likely victoriametrics
rather than vmetric, or another valid namespace) by checking Docker Hub or
project documentation, and update the Version value to reference an actual,
published Docker image tag that exists.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 322fa55d-ca5d-48cb-b61f-a7dac3f6c316

📥 Commits

Reviewing files that changed from the base of the PR and between 86569c6 and 927660b.

📒 Files selected for processing (2)

• README.md
• internal/config/subject.go