is it chore or ci?

Removed the ci change from this pr

in java we just set the minimum version but don't limit the maximum one

in general, it has been already confirmed that selenium does not follow semver, so they may introduce breaking changes even in minor releases. For us this means we must either strictly limit the lib version and then manually release a new version of python client when a new selenium is releases and tested for the compatibility. Or just acknowledge that we are limited in resources and we cannot really cover the testing for each version change..

Based on the above statement my proposal would be to follow the same strategy we have in java:

• the selenium version is set to a range where the minimum one is the recent tested/fixed one and the maximum one is the next major
• we allow selenium client updates without further validations. If a compatibility issue happens we fix it, bump the miniumum supported version (if necessary) and release the new version of the python client
• users can always lock/override selenium's version in their projects as a possible workaround

Correct. Hm, actually maybe what we could as our best is to give users to keep local files in their eng. Let me modify this PR to add acknowledgment in the readme

Updated