Repository navigation
feat!: bump appium-android-driver and appium-chromedriver with ChromeDriver executable verification - #1264
Open
mykola-mokhnach wants to merge 2 commits into
Conversation
…Driver executable verification BREAKING CHANGE: ChromeDriver and Microsoft Edge WebDriver executables are verified against a SHA-256 allowlist before they are run. Custom or unlisted executables are rejected unless the chromedriver_allow_any_executable server feature is enabled.
eglitise
approved these changes
Nov 22, 2026
This branch has not been deployed
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
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.
Summary
Bumps
appium-android-driverto v16 andappium-chromedriverto v11, which verifies ChromeDriver and Microsoft Edge WebDriver executables against a SHA-256 allowlist before running them (appium/appium-android#171).chromedriver_autodownload, are run.appium:chromedriverExecutableand to the executables found inappium:chromedriverExecutableDir.chromedriver_allow_any_executableserver feature (--allow-insecure espresso:chromedriver_allow_any_executable).Docs: new "Executable Verification" section in the hybrid guide, the new insecure feature, and notes for the two capabilities.
Breaking change
Custom, self-built or unlisted ChromeDriver executables are rejected unless
chromedriver_allow_any_executableis enabled on the server.Note: the docs say "since 11.0.0", please adjust if the release version differs.