Updated pom.xml by Safer

[safer-bot]

This PR was automatically created by Safer, an open-source tool that updates vulnerable dependencies with compatible and more secure versions.

Analyzed commit: ea4b326
File updated: pom.xml
Vulnerabilities reduced: 35 -> 12

Let us know if you have questions.

Thanks,
Safer Bot

Summary by CodeRabbit

• Chores
  • Updated the webdrivermanager dependency to version 6.1.0 for improved compatibility and stability.

[safer-bot]

See details in issue #103

[coderabbitai]

Walkthrough

The version of the webdrivermanager dependency in the Maven pom.xml file was updated from 3.8.1 to 6.1.0. No other modifications were made to the file or its configuration.

Changes

Files	Change Summary
pom.xml	Updated webdrivermanager dependency version from 3.8.1 to 6.1.0

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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: 0

🧹 Nitpick comments (1)

pom.xml (1)

133-136: Optional: externalise the version into a Maven property for easier future bumps

Keeping hard-coded versions inside <dependency> blocks scatters version information. Consider introducing a property:

-        <dependency>
-            <groupId>io.github.bonigarcia</groupId>
-            <artifactId>webdrivermanager</artifactId>
-            <version>6.1.0</version>
+        <dependency>
+            <groupId>io.github.bonigarcia</groupId>
+            <artifactId>webdrivermanager</artifactId>
+            <version>${webdrivermanager.version}</version>
         </dependency>
...
-        <vaadin.version>24.3.5</vaadin.version>
+        <vaadin.version>24.3.5</vaadin.version>
+        <webdrivermanager.version>6.1.0</webdrivermanager.version>

This small refactor centralises version management and keeps future Safer-bot updates minimal.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ea4b326 and 9d30929.

📒 Files selected for processing (1)

• pom.xml (1 hunks)

🔇 Additional comments (1)

pom.xml (1)

133-136: WebDriverManager 6.1.0 upgrade looks safe

I verified that:

• No calls to the removed driverVersion(...) API are present (rg returned zero matches).
• The only WebDriverManager usage is in src/test/java/com/flowingcode/vaadin/addons/xterm/integration/AbstractViewTest.java:61 (WebDriverManager.chromedriver().setup();), which remains unchanged.
• The project’s compiler source is set to Java 17, satisfying the Java ≥ 11 requirement.

You can proceed with the merge. Please run the full build and test suite to ensure nothing else is impacted.