Update version 4.43.0 in docs and samples

[VietND96]

[deploy site]

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

Motivation and Context

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

[qodo-code-review]

Review Summary by Qodo

Update Selenium version to 4.43.0 in docs and samples

📝 Documentation

Walkthroughs

Description

• Update Selenium version from 4.41.0 to 4.43.0 across documentation
• Update release date from February 20 to April 10, 2026
• Update download links and version references in all language bindings
• Update Selenium Server JAR filename in test configuration files

Diagram

flowchart LR
  A["Version 4.41.0"] -- "Update to" --> B["Version 4.43.0"]
  B -- "Update in" --> C["Documentation Pages"]
  B -- "Update in" --> D["Test Configuration Files"]
  B -- "Update in" --> E["Language Bindings Info"]
  C -- "Affects" --> F["Downloads & Bindings"]
  D -- "Affects" --> G["Python, .NET, Ruby Tests"]

Loading

File Changes

1. website_and_docs/layouts/downloads/list.html 📝 Documentation +2/-2

Update downloads page to version 4.43.0

• Updated Selenium Server download link from 4.41.0 to 4.43.0
• Updated NuGet release version and date to 4.43.0 (April 10, 2026)
• Updated download URL references for the latest stable version

website_and_docs/layouts/downloads/list.html

---

2. website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html 📝 Documentation +7/-7

Update all language bindings to version 4.43.0

• Updated .NET/C# binding version to 4.43.0 with new release date
• Updated Ruby binding version and download link to 4.43.0
• Updated Java binding version and download link to 4.43.0
• Updated Python and JavaScript binding versions to 4.43.0

website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html

---

3. examples/python/tests/conftest.py ⚙️ Configuration changes +3/-3

Update Python test fixtures to use 4.43.0 JAR

• Updated Selenium Server JAR filename from 4.41.0 to 4.43.0 in server_old fixture
• Updated Selenium Server JAR filename from 4.41.0 to 4.43.0 in server fixture
• Updated Selenium Server JAR filename from 4.41.0 to 4.43.0 in grid_server fixture

examples/python/tests/conftest.py

---

View more (2)

4. examples/dotnet/SeleniumDocs/BaseTest.cs ⚙️ Configuration changes +1/-1

Update .NET test base class JAR version

• Updated ServerJarName constant from 4.41.0 to 4.43.0

examples/dotnet/SeleniumDocs/BaseTest.cs

---

5. examples/ruby/spec/drivers/remote_webdriver_spec.rb ⚙️ Configuration changes +1/-1

Update Ruby test fixture to use 4.43.0 JAR

• Updated Selenium Server JAR filename from 4.41.0 to 4.43.0 in server fixture

examples/ruby/spec/drivers/remote_webdriver_spec.rb

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Inconsistent jar path fixture 🐞 Bug ☼ Reliability

Description

In examples/python/tests/conftest.py, server_old() builds the selenium-server jar path relative to
examples/python, while server() and grid_server() build it relative to examples/. If server_old is
used, it will look for the jar in a different location than the other fixtures and is likely to fail
to start the server.

Code

examples/python/tests/conftest.py[R149-153]

                os.path.abspath(__file__)
            )
        ),
-        "selenium-server-4.41.0.jar",
+        "selenium-server-4.43.0.jar",
    )

Evidence

server_old() goes up 2 directories from conftest.py (…/python/tests -> …/python) when building the
jar path, but server() and grid_server() go up 3 directories (…/python/tests -> …/examples),
indicating server_old is pointing at a different jar location than the other server fixtures.

examples/python/tests/conftest.py[142-153]
examples/python/tests/conftest.py[198-212]
examples/python/tests/conftest.py[265-285]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`server_old()` constructs a different jar path than `server()`/`grid_server()`, which can break server startup if `server_old` is used.

### Issue Context
In `examples/python/tests/conftest.py`, the newer fixtures resolve the jar from the shared `examples/` directory, but `server_old` resolves it from `examples/python/`.

### Fix Focus Areas
- examples/python/tests/conftest.py[142-212]

### Suggested fix
- Either:
 - Update `server_old` to compute `_path` the same way `server()` does (go up 3 directories), or
 - Remove `server_old` entirely if it is no longer used.
- Optionally factor jar-path building into a small helper used by all three fixtures to prevent future drift.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Samples pinned to 4.41.0 ☑ 🐞 Bug ⚙ Maintainability

Description

The website templates now advertise 4.43.0 as the stable language binding versions, but the sample
projects still pin Selenium client libraries to 4.41.0. This creates a docs/samples mismatch where
readers following the samples will install older bindings than the site claims are stable.

Code

website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html[R27-31]

        <p class="card-text m-0 pb-1">
          Stable:
          <a href="https://www.nuget.org/packages/Selenium.WebDriver" class="card-link">
-            4.41.0 (February 20, 2026)
+            4.43.0 (April 10, 2026)
          </a>

Evidence

The docs templates were updated to show 4.43.0 as the stable binding version, but multiple sample
build files still explicitly pin 4.41.0 (NuGet, PyPI, Maven, RubyGems, npm), so the repository’s
samples are not aligned with the newly-published stable version in the docs.

website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html[27-32]
examples/dotnet/SeleniumDocs/SeleniumDocs.csproj[8-15]
examples/python/requirements.txt[1-2]
examples/java/pom.xml[11-18]
examples/ruby/Gemfile[5-11]
examples/javascript/package.json[8-13]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
Docs now state 4.43.0 is the stable binding version, but sample projects still pin Selenium dependencies to 4.41.0.

### Issue Context
This PR updates the website’s displayed stable versions, so keeping sample dependency pins on an older version makes the “samples” inconsistent with the “stable” versions advertised to users.

### Fix Focus Areas
- examples/dotnet/SeleniumDocs/SeleniumDocs.csproj[8-15]
- examples/python/requirements.txt[1-2]
- examples/java/pom.xml[11-18]
- examples/java/build.gradle[10-16]
- examples/kotlin/pom.xml[19-23]
- examples/ruby/Gemfile[5-11]
- examples/javascript/package.json[8-13]

### Suggested fix
- Update pinned Selenium client library versions from `4.41.0` to `4.43.0` across the sample projects.
- If you update npm dependencies, regenerate `package-lock.json` accordingly to keep it consistent with `package.json`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	2bb9168
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/69e58e06a7e59e0008e3f732
😎 Deploy Preview	https://deploy-preview-2622--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[harsha509]

LGTM!

[harsha509]

LGTM now!
mostly fixed all the tests
failing dotnet windows test are not related to this PR!

[harsha509]

Thank you @VietND96 !