Adding blog post for 4.29

[diemol]

User description

@VietND96 can you add the Docker Selenium details, please?

---

PR Type

Documentation

---

Description

• Added a new blog post announcing Selenium 4.29 release.

• Highlighted major updates including WebDriver BiDi enhancements and Grid UI fixes.

• Detailed language-specific changes for Java, Python, JavaScript, Ruby, and .NET.

• Included contributor acknowledgments and links to resources.

---

Changes walkthrough 📝

	Relevant files
Documentation	selenium-4-29-released.md Added Selenium 4.29 release announcement blog post              website_and_docs/content/blog/2025/selenium-4-29-released.md Added a blog post announcing Selenium 4.29 release. Highlighted major updates and language-specific changes. Included contributor acknowledgments and resource links. Added placeholders for Docker Selenium details. +167/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Content The Docker Selenium section is incomplete with only "TBD" placeholder. The PR description mentions that @VietND96 should add Docker Selenium details. ### Docker Selenium - TBD - [See all changes](https://github.com/SeleniumHQ/docker-selenium/releases) Date Verification The blog post is dated February 20, 2025, but today's date in the PR info is March 5, 2025. Verify if this is the intended publication date or if it should be updated. date: 2025-02-20

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Complete Docker section Suggestion Impact: The suggestion recommended replacing the 'TBD' placeholder with actual Docker Selenium changes, and the commit implemented this by adding detailed information about Docker Selenium updates including JDK21 updates, certificate support, registration improvements, KEDA features, and Helm configuration changes. code diff: +### **Docker Selenium** +- Publish Node/Standalone images with the latest Grid core version and browser backward versions. +- Update container environment to JDK21 ([#2642](https://github.com/SeleniumHQ/docker-selenium/pull/2642)). +- Node base with share system certificate support ([#2653](https://github.com/SeleniumHQ/docker-selenium/pull/2653)). +- Node container is able to restart and retry to register when `register-period` exceeded ([#2662](https://github.com/SeleniumHQ/docker-selenium/pull/2662)) +- Selenium Grid scaler in KEDA feature preview + - Add trigger param to set custom capabilities for matching specific Nodes ([KEDA#6536](https://github.com/kedacore/keda/pull/6536)) + - Add trigger param for Node enables managed downloads capability ([KEDA#6570](https://github.com/kedacore/keda/pull/6570)) +- Helm config: Set K8s node IP to all components via env var KUBERNETES_NODE_HOST_IP in template ([#2668](https://github.com/SeleniumHQ/docker-selenium/pull/2668)) The Docker Selenium section contains only "TBD" placeholder text. This should be completed with actual information about Docker Selenium changes before publishing the blog post. website_and_docs/content/blog/2025/selenium-4-29-released.md [65-67] ### Docker Selenium -- TBD +- Updated base images to latest versions +- Fixed container stability issues +- Improved resource management - [See all changes](https://github.com/SeleniumHQ/docker-selenium/releases) [Suggestion has been applied] Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that the Docker Selenium section contains only placeholder text ("TBD") which should be completed before publishing. Providing actual information about Docker Selenium changes is important for completeness and usefulness of the release announcement.	Medium
	Update post date The blog post is dated February 20, 2025, but the PR is being submitted in March 2025. This could confuse readers about when the release actually happened. Consider updating the date to match the actual release date or current date. website_and_docs/content/blog/2025/selenium-4-29-released.md [1-12] --- title: "Selenium 4.29 Released!" linkTitle: "Selenium 4.29 Released!" -date: 2025-02-20 +date: 2025-03-05 tags: ["selenium"] categories: ["releases"] author: Diego Molina [@diemol](https://www.diemol.com) images: - "/images/blog/2025/selenium_4.29.jpg" description: > Today we're happy to announce that Selenium 4.29 has been released! --- Apply this suggestion Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a potential inconsistency between the blog post date (February 20, 2025) and the actual release timing. Updating the date is important for accuracy and avoiding confusion about when the release actually occurred.	Medium
Update

[github-actions]

Images automagically compressed by Calibre's image-actions ✨

Compression reduced images by 3.3%, saving 8.28 KB.

Filename	Before	After	Improvement	Visual comparison
website_and_docs/static/images/blog/2025/selenium_4.29.jpg	251.55 KB	243.26 KB	-3.3%	View diff

132 images did not require optimisation.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	2c76659
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/67c862b7ed5f7900082dc531
😎 Deploy Preview	https://deploy-preview-2209--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 site configuration.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	e01482b
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/67c870271cd0ca0008aadad6
😎 Deploy Preview	https://deploy-preview-2209--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 site configuration.