chore(deps): autoupdate 2026-09-07

[vzakharchenko]

Automated dependency update produced by .github/workflows/autoupdate.yml via scripts/update-dependencies.sh. Will auto-merge once required checks pass (see .github/workflows/automerge.yml).

Summary by CodeRabbit

• Chores
  • Updated the Sonar Maven plugin to a newer version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: dd888085-00e5-4823-bb10-c784d2f0d5c8

📥 Commits

Reviewing files that changed from the base of the PR and between d3fea61 and f9ee69e.

📒 Files selected for processing (1)

• pom.xml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Maven properties update the Sonar Maven plugin from version 5.7.0.6970 to 5.8.0.7211.

Changes

Sonar Maven Plugin Upgrade

Layer / File(s)	Summary
Plugin version configuration pom.xml	The sonar-maven-plugin.version property now uses version 5.8.0.7211.

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

Merge Risk: ⚪ Minimal · up to f9ee6

This updates the Sonar Maven plugin used by CI analysis. The surrounding Sonar configuration remains compatible, with no current merge-blocking risk identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains that automation generated the dependency update and that auto-merge is configured. It does not include most required template sections, including the summary, issue status, ch…	Complete the repository template. State the Sonar Maven plugin version change, use "n/a" for the issue if applicable, select the CI / build / tooling type, identify the root module or explain that no listed module applies, confirm whether t…

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately identifies an automated dependency update and includes the update date. It is related to the Sonar Maven plugin version change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Description check

Explanation

The description explains that automation generated the dependency update and that auto-merge is configured. It does not include most required template sections, including the summary, issue status, change type, modules touched, breaking-change status, testing, and checklist.

Resolution

Complete the repository template. State the Sonar Maven plugin version change, use "n/a" for the issue if applicable, select the CI / build / tooling type, identify the root module or explain that no listed module applies, confirm whether the change is breaking, record testing or CI validation, and complete the checklist.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependencies/auto-2026-09-07

---

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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.