[🐛 Bug]: Mismatch between __version__ and release version

[Th3DarkOn3]

What happened?

After the versione checking of selenium on python terminal I noticed a mismatching of actual released versione and the visible version (released = 4.16 ; version = 4.15.2).
Please update the file py/selenium/init.py

How can we reproduce the issue?

Go to the python terminal an type:

import selenium

selenium.__version__

Relevant log output

no logs available

Operating System

Windows 11

Selenium version

Python 4.16

What are the browser(s) and version(s) where you see this issue?

not relevant

What are the browser driver(s) and version(s) where you see this issue?

not relevant

Are you using Selenium Grid?

No response

[github-actions]

@Th3DarkOn3, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

We are now using a script to bump versions in different parts. Unfortunately, it missed a couple of files and hence the issue you see. We cannot fix this in 4.16.0, but in the linked commit we have fixed the script to avoid this in the future. Thank you for reporting this.

[titusfortner]

Oops, this is my fault; I now remember that when I did the release for 4.15 I had to manually fix something, but then didn't go back and update the script, and forgot for 4.16. Thanks for fixing, Diego.

[github-actions]

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.