4.36/4.37/4.38/4.39/4.40 release notes

[diemol]

PR Type

Documentation

---

Description

• Add comprehensive Selenium 4.36 release notes blog post

• Document BiDi expansion across Java, Python, .NET, Ruby

• Highlight Grid improvements and developer experience enhancements

• List language-specific updates and contributor acknowledgments

---

Diagram Walkthrough

flowchart LR
  A["Release Notes Content"] --> B["BiDi Capabilities"]
  A --> C["Language Updates"]
  A --> D["Grid Improvements"]
  A --> E["Contributors"]
  B --> F["Java, Python, .NET, Ruby"]
  C --> G["Logging, Error Handling, Refactors"]
  D --> H["Regression Fix, UI Toggle"]

Loading

File Walkthrough

Relevant files

Documentation

selenium-4-36-released.md Selenium 4.36 release announcement blog post                          website_and_docs/content/blog/2025/selenium-4-36-released.md Created new blog post announcing Selenium 4.36 release Documented expanded BiDi support across all language bindings Listed language-specific updates for Java, Python, .NET, Ruby, JavaScript, and Rust Included Selenium Grid improvements and Docker Selenium changes Added contributor acknowledgments from multiple Selenium projects +276/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct the Netty version number Correct the Netty version number mentioned in the release notes, as 4.2.4 is likely a typo and should be a version from the 4.1.x series. website_and_docs/content/blog/2025/selenium-4-36-released.md [123] -- **Updated to Netty 4.2.4** for better network handling. +- **Updated to Netty 4.1.114.Final** for better network handling. Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies a likely typo in the Netty version number, as 4.2.4 is not a standard version, and prompts for verification to ensure technical accuracy in the release notes.	Low
	✅ Update image to match release version Suggestion Impact: The frontmatter image reference was changed from /images/blog/2025/selenium_4.35.jpg to /images/blog/2025/selenium_4.36.jpg as suggested. code diff: images: - - "/images/blog/2025/selenium_4.35.jpg" + - "/images/blog/2025/selenium_4.36.jpg" Update the image path in the blog post's frontmatter to reference the correct image for the Selenium 4.36 release instead of 4.35. website_and_docs/content/blog/2025/selenium-4-36-released.md [8-9] images: - - "/images/blog/2025/selenium_4.35.jpg" + - "/images/blog/2025/selenium_4.36.jpg" [Suggestion processed] Suggestion importance[1-10]: 5 __ Why: The suggestion correctly identifies a likely copy-paste error in the image path, which references the previous version (4.35) instead of the current release (4.36), improving the post's accuracy.	Low
Update

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	51b3909
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/6980a8c225df950008791be4
😎 Deploy Preview	https://deploy-preview-2582--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.

[github-actions]

Images automagically compressed by Calibre's image-actions ✨

Compression reduced images by 13.3%, saving 10.8 KB.

Filename	Before	After	Improvement	Visual comparison
website_and_docs/static/images/blog/2025/selenium_4.39.jpg	81.5 KB	70.6 KB	13.3%	View diff

3 images did not require optimisation.