Skip to content
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

chore: Bump the minimum selenium client version to 4.26.0 #2246

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

mykola-mokhnach
Copy link
Contributor

Change list

After SeleniumHQ/selenium#13949 is resolved there is a chance to finally get rid of the most ugly reflection usages.

Types of changes

  • 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)

@mykola-mokhnach
Copy link
Contributor Author

I've also noticed there is one more variable whose scope I would like to extend.
It is mentioned in SeleniumHQ/selenium#14811
As soon as this prop is fixed we can get rid of the reflection usage completely

@mykola-mokhnach mykola-mokhnach merged commit 42480fe into master Nov 27, 2024
7 checks passed
@mykola-mokhnach mykola-mokhnach deleted the sel_upd branch November 27, 2024 07:49
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.

2 participants