Posting a PSA to remind the community to frequently update the Selenium Client

[StuMinch]

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

This blog post is a PSA to remind the community to frequently update the Selenium Client.

Motivation and Context

A common theme in our industry is that users set the initial Selenium client version, build their test suite, and rarely revisit the Selenium client version they are using. The long-term effect of this is that users continue using outdated versions of the Selenium client which can cause flaky behavior and unexplained issues with their test executions.

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.

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	b6dee56

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ StuMinch
❌ Stuart Minchington

---

Stuart Minchington seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[qodo-code-review]

PR Summary by Qodo

Add PSA blog post encouraging regular Selenium client upgrades

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Publish a PSA blog post explaining how outdated clients cause flakiness
• Encourage a recurring habit of upgrading Selenium alongside browser updates
• Link readers to the Selenium downloads page and official social channels

Diagram

graph TD
A["Author"] --> B["Blog post (Markdown)"] --> C(["Hugo build"]) --> D["selenium.dev site"] --> E{{"Community readers"}}
subgraph Legend
direction LR
_file["Content file"] ~~~ _build(["Build tool"]) ~~~ _ext{{"External audience"}}
end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Add an evergreen notice on the Downloads page

• ➕ Reaches users at the exact moment they choose a client version
• ➕ Remains visible long after the blog post falls off the front page
• ➖ Less room for narrative/context than a blog post
• ➖ Requires careful wording to avoid cluttering a high-traffic page

2. Add a short “upgrade cadence” callout in relevant docs pages

• ➕ Targets readers learning WebDriver usage where flakiness guidance fits naturally
• ➕ Can be translated/localized alongside existing docs content
• ➖ Requires touching multiple docs sections and translations
• ➖ Harder to keep messaging consistent across many pages

Recommendation: The blog-post PSA approach is appropriate for awareness and shareability; consider a follow-up lightweight banner/callout on the Downloads page to make the guidance evergreen and catch users who don’t read the blog.

Files changed (1) +70 / -0

Documentation (1) +70 / -0

selenium-client-update-psa.mdAdd PSA post on Selenium client upgrade cadence and flakiness +70/-0

Add PSA post on Selenium client upgrade cadence and flakiness

• Introduces a new blog post explaining how browser/client drift contributes to flaky tests and why upgrading Selenium often resolves instability. Includes frontmatter metadata (title/date/tags/categories/hero image), links to the downloads page, and social follow links.

website_and_docs/content/blog/2026/selenium-client-update-psa.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (1) 📜 Skill insights (0)

1. Front matter title wrong case 📘 Rule violation ✧ Quality

Description

The new blog post sets the front matter title in Title Case, but the style guide requires Sentence
capitalization for title (with Title Capitalization reserved for linkTitle). This creates
inconsistent metadata formatting across the documentation site.

Code

website_and_docs/content/blog/2026/selenium-client-update-psa.md[R2-3]

+title: "Why Keeping Selenium Updated Matters"
+linkTitle: "Why Keeping Selenium Updated Matters"

Evidence

The style guide explicitly states that linkTitle uses Title Capitalization while title must use
Sentence capitalization. The new file sets both title and linkTitle to the same Title Case
string.

Rule 2141344: Documentation changes must follow the central style guide file
website_and_docs/content/documentation/about/style.en.md[33-38]
website_and_docs/content/blog/2026/selenium-client-update-psa.md[2-3]

Agent prompt

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

## Issue description
The front matter `title` uses Title Case, but the style guide requires Sentence capitalization for `title` (and Title Capitalization for `linkTitle`).

## Issue Context
Per the central documentation style guide, `linkTitle` should be short and Title Capitalized, while `title` should use Sentence capitalization.

## Fix Focus Areas
- website_and_docs/content/blog/2026/selenium-client-update-psa.md[2-3]

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

---

2. Unused link references 🐞 Bug ⚙ Maintainability

Description

The post defines reference-style links for bindings/team/BiDi that are never referenced in the
article body, leaving unnecessary dead content at the bottom of the file.

Code

website_and_docs/content/blog/2026/selenium-client-update-psa.md[R66-69]

+[bindings]: /downloads#bindings
+
+[team]: /project/structure
+

Evidence

The article body uses the [downloads] reference, but [bindings], [team], and [BiDi] appear
only in their definitions and are never referenced elsewhere in the file.

website_and_docs/content/blog/2026/selenium-client-update-psa.md[19-21]
website_and_docs/content/blog/2026/selenium-client-update-psa.md[64-70]

Agent prompt

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

## Issue description
The blog post defines reference-style links (`[bindings]`, `[team]`, `[BiDi]`) that are not used anywhere in the article body.

## Issue Context
Only the `[downloads]` reference is used in the post body; the other references appear only as definitions at the bottom.

## Fix Focus Areas
- website_and_docs/content/blog/2026/selenium-client-update-psa.md[64-70]

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

---

Context

✅ Compliance rules (platform): 10 rules

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Front matter title wrong case 📘 Rule violation ✧ Quality

The new blog post sets the front matter title in Title Case, but the style guide requires Sentence
capitalization for title (with Title Capitalization reserved for linkTitle). This creates
inconsistent metadata formatting across the documentation site.

Agent Prompt

## Issue description
The front matter `title` uses Title Case, but the style guide requires Sentence capitalization for `title` (and Title Capitalization for `linkTitle`).

## Issue Context
Per the central documentation style guide, `linkTitle` should be short and Title Capitalized, while `title` should use Sentence capitalization.

## Fix Focus Areas
- website_and_docs/content/blog/2026/selenium-client-update-psa.md[2-3]

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

[qodo-code-review]

2. Unused link references 🐞 Bug ⚙ Maintainability

The post defines reference-style links for bindings/team/BiDi that are never referenced in the
article body, leaving unnecessary dead content at the bottom of the file.

Agent Prompt

## Issue description
The blog post defines reference-style links (`[bindings]`, `[team]`, `[BiDi]`) that are not used anywhere in the article body.

## Issue Context
Only the `[downloads]` reference is used in the post body; the other references appear only as definitions at the bottom.

## Fix Focus Areas
- website_and_docs/content/blog/2026/selenium-client-update-psa.md[64-70]

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