[🐛 Bug]: tags missing for 4.1.1-4.1.3

[bollwyvl]

What happened?

The official packages on e.g. PyPI have been updated with versions newer than 4.1.0, but the sources have not been tagged.

https://github.com/SeleniumHQ/selenium/tags

See also #9917: issues like these are making it harder for downstreams to package selenium.

How can we reproduce the issue?

- Visit PyPi
- pick a version
- download the wheel
- visit github
- try to find the commit from which the wheel was built

Relevant log output

n/a

Operating System

all

Selenium version

4.1.1+

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

n/a

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

n/a

Are you using Selenium Grid?

no

[github-actions]

@bollwyvl, 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, 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!

[titusfortner]

For the mono-repo we are only creating tags that apply to the whole project. Each language releases a 4.1.0, but patch releases (e.g., 4.1.1) are for language binding specific updates.

Is there a particular use case you have in mind? Remember that some of the files in the released package are generated by the build process, and are not stored in the repo. If you need to see exactly what code is being used in the release, you should be able to just unzip the wheel file. Alternatively, you can look at the commit where the version has been updated in the code: https://github.com/SeleniumHQ/selenium/blame/trunk/py/BUILD.bazel#L8

[bollwyvl]

Thanks for the reply. As with the sdists issue, predictable version-based URLs that yield hashable input artifacts are far easier for downstream package managers to automate against. Wheels discard a fair amount of build information, and parsing bazel files sounds brittle as well... But if that's the best we're going to get...

[AutomatedTester]

@bollwyvl We can start stamping the wheels so that they have a some more build info in them. I haven't done this yet as it can impact the build caching but we can add it in if you think it help

[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.