Skip to content

[🐛 Bug]: SM Electron does not honor --browser-version when fetching driver #17549

Description

@titusfortner

Description

Selenium Manager's Electron driver fetch ignores --browser-version. The URL is always built from the /releases/latest redirect, so the user-requested Electron version never selects the matching release's chromedriver asset.

The version is only used as a metadata cache key — not for selecting which release to download.

Relevant Code

  • rust/src/electron.rs:124-130request_driver_version() always reads read_redirect_from_link(latest_url, ...), discarding any requested version.
  • rust/src/electron.rs:150-163get_driver_url() then formats the URL using whatever get_driver_version() returned (always latest).

Expected: when --browser-version 29.1.4 (or major like 29) is supplied, fetch the matching release's chromedriver asset from https://github.com/electron/electron/releases/download/v<version>/chromedriver-v<version>-<platform>.zip.

Reproducible Code

./selenium-manager --browser electron --browser-version 29.0.0 --debug

Observe that the driver downloaded is from the latest Electron release, not 29.0.0.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-managerSelenium ManagerC-rustRust code is mostly Selenium ManagerI-defectSomething is not working as intended

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions