chore(collector): Update COLLECTOR_VERSION

[rhacs-bot]

Daily update of COLLECTOR_VERSION to latest master version

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: ca4f54c6-31c1-4a5e-9aee-773d4f130e34

📥 Commits

Reviewing files that changed from the base of the PR and between 85ac453 and 2b15466.

📒 Files selected for processing (1)

• COLLECTOR_VERSION

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated the collector version to the latest release.

Walkthrough

The COLLECTOR_VERSION record now contains 3.25.0-83-g4ea28a27d2 instead of 3.25.0-71-gf833aaf49f.

Changes

Collector version

Layer / File(s)	Summary
Update collector version COLLECTOR_VERSION	The recorded collector version was updated to 3.25.0-83-g4ea28a27d2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description states the change but omits the required documentation, testing, and validation sections.	Add the required template sections and document documentation status, testing status, and validation details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the update to COLLECTOR_VERSION, which is the main change.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update_collector_version

---

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

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

[github-actions]

🚀 Build Images Ready

Images are ready for commit 2b15466. To use with deploy scripts:

export MAIN_IMAGE_TAG=4.12.x-648-g2b154662a0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.22%. Comparing base (85ac453) to head (2b15466).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #22052      +/-   ##
==========================================
- Coverage   51.26%   51.22%   -0.05%     
==========================================
  Files        2869     2869              
  Lines      179230   179230              
==========================================
- Hits        91889    91816      -73     
- Misses      79286    79338      +52     
- Partials     8055     8076      +21     

Flag	Coverage Δ
go-unit-tests	51.22% <ø> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

/konflux-retest roxctl-on-push

[github-actions]

/konflux-retest operator-on-push

[github-actions]

/konflux-retest scanner-v4-on-push

[openshift-ci]

@rhacs-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ocp-4-22-nongroovy-e2e-tests	2b15466	link	false	/test ocp-4-22-nongroovy-e2e-tests
ci/prow/ocp-4-22-qa-e2e-tests	2b15466	link	false	/test ocp-4-22-qa-e2e-tests
ci/prow/ocp-4-12-qa-e2e-tests	2b15466	link	false	/test ocp-4-12-qa-e2e-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.