build: set vaadin dependency to 14.11.13

[javier-godoy]

Summary by CodeRabbit

• Chores
  • Updated framework and testing dependencies to latest stable versions for improved compatibility and performance.

[coderabbitai]

Walkthrough

Updated Maven dependencies in pom.xml: Vaadin platform version bumped from 14.7.7 to 14.11.13, and webdrivermanager dependency updated from 3.8.1 to 6.3.2.

Changes

Cohort / File(s)	Summary
Maven dependency updates pom.xml	Updated Vaadin platform property from 14.7.7 to 14.11.13; Updated webdrivermanager dependency from 3.8.1 to 6.3.2

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify compatibility between Vaadin 14.7.7 → 14.11.13 (significant version jump; check for breaking changes in release notes)
• Verify compatibility between webdrivermanager 3.8.1 → 6.3.2 (major version jump; confirm API compatibility)
• Ensure no other files require updates due to these dependency version changes

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title states it updates Vaadin to 14.11.13, but it also updates webdrivermanager from 3.8.1 to 6.3.2, which is a significant but unmentioned change.	Consider whether the title should mention both dependency updates or if webdrivermanager is a secondary/incidental change. Clarify the primary intent of this PR.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 20251104

---

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 and usage tips.}

[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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a79e62 and 3c75b23.

📒 Files selected for processing (1)

• pom.xml (2 hunks)

🔇 Additional comments (1)

pom.xml (1)

143-143: WebDriverManager 6.3.2 upgrade is API-compatible; verify driver resolution via test execution.

The codebase uses WebDriverManager.chromedriver().setup() in AbstractViewTest.java line 62, which remains supported in v6.3.2. This backward-compatible pattern continues to work in v5/v6. No deprecated methods, custom configurations, or advanced APIs are evident.

However, driver-resolution endpoints and algorithms changed starting in v5/v6; cached-driver resolution behavior may differ and tests that relied on old resolution/cached binaries may get different driver versions. Run the integration test suite to confirm the resolved driver versions are compatible with your environment and Vaadin TestBench. Optionally, clear the local driver cache before testing to ensure clean resolution with v6.3.2 logic. An XXE vulnerability (CVE-2025-4641) affecting versions before 6.1.0 was fixed, making this a security improvement.