Skip to content

docs: Initiate Selenium client compatibility matrix #1918

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 15, 2023
Merged

docs: Initiate Selenium client compatibility matrix #1918

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,20 @@ dependencies {
}
```

### How to pin Selenium dependencies?
### Compatibility Matrix
| Appium Java Client | Selenium client |
|--------------------|---------------------------------------------|
| `8.5.0` | `4.9.1` |
| `8.4.0` | `4.8.2`, `4.8.3`, `4.9.0` |
| `8.3.0` | `4.7.0`, `4.7.1`, `4.7.2`, `4.8.0`, `4.8.1` |
| `8.2.1` | `4.5.0`, `4.5.1`, `4.5.2`, `4.5.3`, `4.6.0` |

#### Why is it so complicated?

Selenium client does not follow [Semantic Versioning](https://semver.org/), so breaking changes might be introduced
even in patches, which requires Appium team to update Java client in response.

#### How to pin Selenium dependencies?

Appium Java Client declares Selenium dependencies using open version range which is handled in differently by different
build tools. Sometimes users may want to pin used Selenium dependencies for [various reasons](https://github.com/appium/java-client/issues/1823).
Expand Down