[🐛 Bug]: Deprecated functionality removed in a minor version
See original GitHub issueWhat happened?
Hi folks,
First of all, big thanks to all the active maintainers on this project. Selenium is an awesome tool and the amount of complexity you all are dealing with on a daily basis is mind-boggling. With that in mind, I hate to even be filing this issue, but I wanted to try to do my part to help out the community.
Based on my understanding of SemVer, it calls for a major version bump when backwards-incompatible changes are introduced (e.g. removing deprecated features, or possibly even the change to move_to
behavior). Maybe I’m misunderstanding something but it seems like the 4.3 release isn’t respecting that rule.
We were certainly surprised to find that those changes had been made in a minor version update, and while I imagine there may be some good reasons for the Selenium team choosing to do this it also has some potential downsides for users of the package.
Just wanted to put this out there to see if either I’m missing something here, or maybe there is some room for improvement in the way releases are handled going forward?
Thanks!
How can we reproduce the issue?
The changelogs for 4.3 detail the removed functionality: https://github.com/SeleniumHQ/selenium/releases/tag/selenium-4.3.0
Relevant log output
no relevant log output
Operating System
MacOS
Selenium version
4.3
What are the browser(s) and version(s) where you see this issue?
Chrome
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver
Are you using Selenium Grid?
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Donezo: https://github.com/SeleniumHQ/selenium/pull/10872
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.