chore(deps): autoupdate 2026-09-12

[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 Maven Exec plugin to version 3.6.4.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: d652b9ee-6a71-4edf-9fdf-8729e2081052

📥 Commits

Reviewing files that changed from the base of the PR and between 2d60e15 and b06ad3d.

📒 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 configuration updates the Exec plugin version from 3.6.3 to 3.6.4.

Changes

Maven plugin update

Layer / File(s)	Summary
Exec plugin version update pom.xml	The exec-maven-plugin.version property changes from 3.6.3 to 3.6.4.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to b06ad

No actionable merge risk remains from this dependency update.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the automation source and auto-merge behavior, but it omits the required Summary, issue reference, change type, modules touched, breaking change, testing, and checklist inform…	Complete the repository template. State that the Maven Exec plugin changes from 3.6.3 to 3.6.4, mark the change as CI/build/tooling, identify the touched module or explain that none applies, mark the change as non-breaking, record the tests…

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title correctly identifies this pull request as an automated dependency update and includes the update date. It is concise and related to the Maven Exec 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 the automation source and auto-merge behavior, but it omits the required Summary, issue reference, change type, modules touched, breaking change, testing, and checklist information.

Resolution

Complete the repository template. State that the Maven Exec plugin changes from 3.6.3 to 3.6.4, mark the change as CI/build/tooling, identify the touched module or explain that none applies, mark the change as non-breaking, record the tests that ran, and complete the checklist items.

• 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-12

---

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.