Skip to content

Conversation

mialeska
Copy link
Contributor

PR Details

Related Issue Link:
How Has This Been Tested
Checklist
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@mialeska mialeska self-assigned this Aug 25, 2025
@mialeska mialeska added java dependencies Pull requests that update a dependency file labels Aug 25, 2025
@github-project-automation github-project-automation bot moved this to In progress in Aquality Core Aug 25, 2025
Copy link

coderabbitai bot commented Aug 25, 2025

Walkthrough

Dependency versions updated in pom.xml: jackson-databind to 2.19.2, selenium-java to 4.35.0, and io.appium:java-client to 10.0.0 (test scope). No public API signature changes reported.

Changes

Cohort / File(s) Summary
Build dependency updates
pom.xml
Bumped versions: jackson-databind 2.18.2 → 2.19.2, selenium-java 4.34.0 → 4.35.0, io.appium:java-client 9.5.0 → 10.0.0 (test scope). No exported/public entity signature changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

I nudge the POM with whiskered care,
Hopping through versions, light as air.
Selenium shines, Jackson’s new,
Appium’s tests got upgrades too.
Carrot commits, dependencies neat—
Thump-thump! This build’s complete. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch enhancement/update-to-selenium-4.35.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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
pom.xml (2)

120-129: Optional: stabilize transitive resolution from Appium by pinning Selenium via properties/dependencyManagement.

Maven will prefer your direct selenium-java:4.35.0, but Appium declares a semver-open Selenium range. To avoid future drift in multi-module builds, consider centralizing versions as properties and/or dependencyManagement. This is a nicety, not a blocker. (github.com)

Apply this small refactor to make upgrades simpler:

@@
   <properties>
     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     <log4j.version>2.25.1</log4j.version>
+    <jackson.version>2.19.2</jackson.version>
+    <selenium.version>4.35.0</selenium.version>
+    <appium.version>10.0.0</appium.version>
   </properties>
@@
   <dependency>
     <groupId>com.fasterxml.jackson.core</groupId>
     <artifactId>jackson-databind</artifactId>
-    <version>2.19.2</version>
+    <version>${jackson.version}</version>
   </dependency>
@@
   <dependency>
     <groupId>org.seleniumhq.selenium</groupId>
     <artifactId>selenium-java</artifactId>
-    <version>4.35.0</version>
+    <version>${selenium.version}</version>
   </dependency>
@@
   <dependency>
     <groupId>io.appium</groupId>
     <artifactId>java-client</artifactId>
-    <version>10.0.0</version>
+    <version>${appium.version}</version>
     <scope>test</scope>
   </dependency>

120-129: Optional: add a quick compatibility check to CI to catch future Selenium/Appium API removals.

Because Selenium keeps removing long-deprecated APIs (e.g., LocationContext/WebStorage in 4.35.0), a lightweight grep-based guard in CI can fail fast on future bumps. You can reuse the script above and wire it in a dedicated “dependency bump checks” job. (fossies.org)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e7083b6 and 1044c65.

📒 Files selected for processing (1)
  • pom.xml (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2024-11-29T13:27:59.820Z
Learnt from: mialeska
PR: aquality-automation/aquality-selenium-core-java#98
File: pom.xml:124-124
Timestamp: 2024-11-29T13:27:59.820Z
Learning: As of November 2024, the latest stable version of `com.fasterxml.jackson.core:jackson-databind` is `2.18.2`, and versions `2.15.x` are outdated.

Applied to files:

  • pom.xml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: aquality-automation.aquality-selenium-core-java (Analyse code with SonarQube)
  • GitHub Check: aquality-automation.aquality-selenium-core-java (Run tests)
🔇 Additional comments (3)
pom.xml (3)

117-117: Jackson to 2.19.2: good, current, and non-vulnerable.

This aligns with your past preference to stay on the latest stable Jackson. 2.19.2 is currently listed as the latest and the “latest non vulnerable version.” LGTM. (security.snyk.io)


125-129: Appium Java Client 10.0.0 matches Selenium 4.35.0—scope and pairing look correct.

v10.0.0 raises the minimum Selenium to 4.35.0 and removes legacy Location/LocationContext glue, so pairing it with Selenium 4.35.0 (as you did) is correct; keeping it in test scope is also appropriate for this module. (github.com)


120-123: Action Required: Verify Java 11+ Configuration and Selenium API Removals

Our automated scans did not detect any direct usages of the removed html5/WebStorage APIs in the Java code, but absence of results is not absolute proof. Likewise, we couldn’t locate a configured Java version in your pom.xml. Please manually verify the following before merging:

  • pom.xml
    • Confirm you have set Java 11 or higher via either a <java.version> property or the Maven Compiler Plugin’s <maven.compiler.source> and <maven.compiler.target> elements.
    • Example snippet to look for:

    <properties>
      <java.version>11</java.version>
    </properties>
    <!-- or -->
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
        <source>11</source>
        <target>11</target>
      </configuration>
    </plugin>
  • Codebase-wide API usages
    • Manually search for any imports or references to:
    org.openqa.selenium.html5.LocationContext
    org.openqa.selenium.html5.Location
    org.openqa.selenium.html5.WebStorage
    org.openqa.selenium.html5.LocalStorage
    org.openqa.selenium.html5.SessionStorage
    org.openqa.selenium.remote.html5.RemoteLocationContext
    • If found, refactor to remove or replace with supported alternatives (e.g., Appium Java Client’s Location API).

Taking these steps will ensure your upgrade to Selenium 4.35.0 (which removes the deprecated LocationContext/WebStorage APIs) does not introduce compile-time or runtime failures.

@mialeska mialeska merged commit 1f2abac into master Aug 25, 2025
6 checks passed
@github-project-automation github-project-automation bot moved this from In progress to Done in Aquality Core Aug 25, 2025
@mialeska mialeska deleted the enhancement/update-to-selenium-4.35.0 branch August 25, 2025 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant