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.

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

Conversation

valfirst
Copy link
Collaborator

Change list

Initiate Selenium client compatibility matrix (to avoid issues like #1914)

Types of changes

What types of changes are you proposing/introducing to Java client?

  • No changes in production code.
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

README.md Outdated
@@ -12,6 +12,14 @@ Since version 8 Appium Java Client had several major changes, which might requir
update your client code. Make sure to follow the [v7 to v8 Migration Guide](https://github.com/appium/java-client/blob/master/docs/v7-to-v8-migration-guide.md)
in order to streamline the migration process.

## Compatibility Matrix
| Appium Java Client | Selenium client |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe it also makes sense to add a link here to the documentation that describes how selenium version could be locked locally

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merged sections

@valfirst valfirst force-pushed the docs-selenium-client-compatibility-matrix branch 5 times, most recently from 7a02cfd to 8475d1a Compare May 12, 2023 14:15
@valfirst valfirst requested a review from mykola-mokhnach May 12, 2023 14:15
@mykola-mokhnach
Copy link
Contributor

Not sure if it makes sense, but we can also explain that Selenium versioning does not follow semver rules, so they might introduce breaking changes even between patches, which requires us to update java client in response

@valfirst valfirst force-pushed the docs-selenium-client-compatibility-matrix branch from 8475d1a to c0d614c Compare May 15, 2023 08:06
@valfirst valfirst merged commit 925bab7 into appium:master May 15, 2023
@valfirst valfirst deleted the docs-selenium-client-compatibility-matrix branch May 15, 2023 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants