[🐛 Bug]: [dotnet] The latest 2 releases were built with DEBUG compilation configuration instead of RELEASE

[nvborisenko]

What happened?

The latest nuget packages contain dll binaries which were built in DEBUG mode.

How can we reproduce the issue?

Explore released artifacts.

Relevant log output

Operating System

any

Selenium version

4.22, 4.23

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

any

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

any

Are you using Selenium Grid?

no

[github-actions]

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

[nvborisenko]

Seems bazzel default compilation optimization mode has been changed: https://github.com/bazelbuild/rules_dotnet/tree/master/docs#debugrelease-configurations

Probably it also affects other bindings.

[nvborisenko]

Thanks @shs96c , it is resolved in v4.24

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.