security(deps): bump org.seleniumhq.selenium:selenium-chrome-driver from 4.39.0 to 4.46.0 - #124
Conversation
Bumps [org.seleniumhq.selenium:selenium-chrome-driver](https://github.com/SeleniumHQ/selenium) from 4.39.0 to 4.46.0. - [Release notes](https://github.com/SeleniumHQ/selenium/releases) - [Commits](SeleniumHQ/selenium@selenium-4.39.0...selenium-4.46.0) --- updated-dependencies: - dependency-name: org.seleniumhq.selenium:selenium-chrome-driver dependency-version: 4.46.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d33e652. Configure here.
| <groupId>org.seleniumhq.selenium</groupId> | ||
| <artifactId>selenium-chrome-driver</artifactId> | ||
| <version>4.39.0</version> | ||
| <version>4.46.0</version> |
There was a problem hiding this comment.
Mismatched Selenium dependency versions
Medium Severity
This bump raises only selenium-chrome-driver to 4.46.0 while selenium-java stays at 4.39.0 and the other drivers remain on 4.38.0/4.39.0. Selenium Java artifacts must share one version; Maven mediation can leave selenium-api/selenium-remote-driver/selenium-chromium-driver on 4.39.0 beside ChromeDriver 4.46.0, risking NoSuchMethodError when Chrome tests run.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit d33e652. Configure here.


Bumps org.seleniumhq.selenium:selenium-chrome-driver from 4.39.0 to 4.46.0.
Release notes
Sourced from org.seleniumhq.selenium:selenium-chrome-driver's releases.
... (truncated)
Commits
df5a634[build] Prepare for release of selenium-4.46.0 (#17763)a6a14b4bumping ts rules (#17760)726666b[rust] Prevent path traversal in tar and pkg extraction (#17668). Reported by...8b85e9a[build] Resolve Chrome milestone from Chrome-for-Testing channel version (#17...9f6ccde[java][bidi] Track events subscriptions using subscription ids (#17759)4177888[java] Move BiDi creation to RemoteWebDriver. Add enable BiDi to SafariOption...185e626[build] fix python linting in format.sh script15ee583[build] document .local customization and add PR review guidance (#17756)ee4057cAdd guidance for testing conventions in each language (#16734)4c140e1[build] Add update_cddl script to refresh pinned w3c/webref CDDL files (#17743)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Low Risk
Single Maven version pin in the Selenium test module; main risk is mixed Selenium artifact versions at runtime, not production app behavior.
Overview
Bumps
org.seleniumhq.selenium:selenium-chrome-driverininfluent-selenium-test/pom.xmlfrom 4.39.0 to 4.46.0 (Dependabot security update). No Java test code changes.Other Selenium artifacts in the same POM (
selenium-java,selenium-firefox-driver,selenium-ie-driver) are unchanged, so Chrome driver is now on a newer minor than the rest of the stack.Reviewed by Cursor Bugbot for commit d33e652. Bugbot is set up for automated code reviews on this repo. Configure here.