chore: vendor ExecutableFinder to drop the selenium-os call site - #2456
Merged
Merged
Conversation
Phase 1 of removing the Selenium dependency footprint: replace org.openqa.selenium.os.ExecutableFinder with an Appium-owned equivalent, trimmed to the bare-name PATH lookup this codebase actually uses. Doesn't shrink the dependency graph yet (selenium-os still comes in transitively via DriverService.Builder until a later phase). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mykola-mokhnach
requested review from
SrinivasanTarget,
saikrishna321 and
valfirst
as code owners
September 30, 2026 16:12
valfirst
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of removing the Selenium dependency footprint: replace org.openqa.selenium.os.ExecutableFinder with an Appium-owned equivalent, trimmed to the bare-name PATH lookup this codebase actually uses. Doesn't shrink the dependency graph yet (selenium-os still comes in transitively via DriverService.Builder until a later phase).