[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.39.0 #3045

selenium-ci · 2025-12-12T01:11:00Z

User description

This PR contains the CHANGELOG for Node/Standalone with backward browser versions

PR Type

Documentation

Description

Add 31 CHANGELOG files for Chrome for Testing versions 113-143
Document Grid 4.39.0 release with build date 20251202
Update Edge version to 143.0.3650.80-1 in browser matrix
Record Docker image tagging for Node and Standalone variants

Diagram Walkthrough

flowchart LR
  A["Grid 4.39.0<br/>Build 20251202"] -->|"Chrome for Testing<br/>versions 113-143"| B["31 CHANGELOG files"]
  B -->|"Node & Standalone<br/>Docker images"| C["Tagged images<br/>with versions"]
  D["browser-matrix.yml"] -->|"Update Edge<br/>version"| E["143.0.3650.80-1"]

File Walkthrough

Relevant files

Documentation

20 files

chrome-for-testing_113.md `Add Chrome for Testing 113 release changelog`	+21/-0
chrome-for-testing_114.md `Add Chrome for Testing 114 release changelog`	+21/-0
chrome-for-testing_115.md `Add Chrome for Testing 115 release changelog`	+21/-0
chrome-for-testing_116.md `Add Chrome for Testing 116 release changelog`	+21/-0
chrome-for-testing_117.md `Add Chrome for Testing 117 release changelog`	+21/-0
chrome-for-testing_118.md `Add Chrome for Testing 118 release changelog`	+21/-0
chrome-for-testing_119.md `Add Chrome for Testing 119 release changelog`	+21/-0
chrome-for-testing_120.md `Add Chrome for Testing 120 release changelog`	+21/-0
chrome-for-testing_121.md `Add Chrome for Testing 121 release changelog`	+21/-0
chrome-for-testing_122.md `Add Chrome for Testing 122 release changelog`	+21/-0
chrome-for-testing_123.md `Add Chrome for Testing 123 release changelog`	+21/-0
chrome-for-testing_124.md `Add Chrome for Testing 124 release changelog`	+21/-0
chrome-for-testing_125.md `Add Chrome for Testing 125 release changelog`	+21/-0
chrome-for-testing_126.md `Add Chrome for Testing 126 release changelog`	+21/-0
chrome-for-testing_127.md `Add Chrome for Testing 127 release changelog`	+21/-0
chrome-for-testing_128.md `Add Chrome for Testing 128 release changelog`	+21/-0
chrome-for-testing_129.md `Add Chrome for Testing 129 release changelog`	+21/-0
chrome-for-testing_130.md `Add Chrome for Testing 130 release changelog`	+21/-0
chrome-for-testing_131.md `Add Chrome for Testing 131 release changelog`	+21/-0
chrome-for-testing_132.md `Add Chrome for Testing 132 release changelog`	+21/-0

Additional files

101 files

chrome-for-testing_133.md	+21/-0
chrome-for-testing_134.md	+21/-0
chrome-for-testing_135.md	+21/-0
chrome-for-testing_136.md	+21/-0
chrome-for-testing_137.md	+21/-0
chrome-for-testing_138.md	+21/-0
chrome-for-testing_139.md	+21/-0
chrome-for-testing_140.md	+21/-0
chrome-for-testing_141.md	+21/-0
chrome-for-testing_142.md	+21/-0
chrome-for-testing_143.md	+21/-0
README.md	+42/-51
chrome-for-testing_113.md	[link]
chrome-for-testing_114.md	[link]
chrome-for-testing_115.md	[link]
chrome-for-testing_116.md	[link]
chrome-for-testing_117.md	[link]
chrome-for-testing_118.md	[link]
chrome-for-testing_119.md	[link]
chrome-for-testing_120.md	[link]
chrome-for-testing_121.md	[link]
chrome-for-testing_122.md	[link]
chrome-for-testing_123.md	[link]
chrome-for-testing_124.md	[link]
chrome-for-testing_125.md	[link]
chrome-for-testing_126.md	[link]
chrome-for-testing_127.md	[link]
chrome-for-testing_128.md	[link]
chrome-for-testing_129.md	[link]
chrome-for-testing_130.md	[link]
chrome-for-testing_131.md	[link]
chrome-for-testing_132.md	[link]
chrome-for-testing_133.md	[link]
chrome-for-testing_134.md	[link]
chrome-for-testing_135.md	[link]
chrome-for-testing_136.md	[link]
chrome-for-testing_137.md	[link]
chrome-for-testing_138.md	[link]
chrome-for-testing_139.md	[link]
chrome-for-testing_140.md	[link]
chrome-for-testing_141.md	[link]
chrome-for-testing_142.md	[link]
chrome_100.md	[link]
chrome_101.md	[link]
chrome_102.md	[link]
chrome_103.md	[link]
chrome_104.md	[link]
chrome_105.md	[link]
chrome_106.md	[link]
chrome_107.md	[link]
chrome_108.md	[link]
chrome_109.md	[link]
chrome_110.md	[link]
chrome_111.md	[link]
chrome_112.md	[link]
chrome_113.md	[link]
chrome_114.md	[link]
chrome_115.md	[link]
chrome_116.md	[link]
chrome_117.md	[link]
chrome_118.md	[link]
chrome_119.md	[link]
chrome_120.md	[link]
chrome_121.md	[link]
chrome_122.md	[link]
chrome_123.md	[link]
chrome_124.md	[link]
chrome_125.md	[link]
chrome_126.md	[link]
chrome_127.md	[link]
chrome_128.md	[link]
chrome_129.md	[link]
chrome_130.md	[link]
chrome_131.md	[link]
chrome_132.md	[link]
chrome_133.md	[link]
chrome_134.md	[link]
chrome_135.md	[link]
chrome_136.md	[link]
chrome_137.md	[link]
chrome_138.md	[link]
chrome_139.md	[link]
chrome_140.md	[link]
chrome_141.md	[link]
chrome_142.md	[link]
chrome_95.md	[link]
chrome_96.md	[link]
chrome_97.md	[link]
chrome_98.md	[link]
chrome_99.md	[link]
edge_114.md	[link]
edge_115.md	[link]
edge_116.md	[link]
edge_117.md	[link]
edge_118.md	[link]
edge_119.md	[link]
edge_120.md	[link]
edge_121.md	[link]
edge_122.md	[link]
edge_123.md	[link]
Additional files not shown

…with Grid 4.39.0 Browser versions: [113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143]

qodo-code-review · 2025-12-12T01:11:32Z

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: 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
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No runtime logging: The PR adds documentation/CHANGELOG content and a version bump without introducing or modifying any code paths that would impact audit logging, so compliance cannot be assessed from the diff alone. Referred Code ./tag_and_push_browser_images.sh 4.39.0 20251202 selenium false chrome-for-testing true Tagging images for browser chrome-for-testing, version 4.39.0, build date 20251202, namespace selenium Selenium Grid version -> 4.39.0-20251202 Chrome for Testing version -> 113.0.5672.63 Short Chrome for Testing version -> 113.0 ChromeDriver version -> 113.0.5672.63 Short ChromeDriver version -> 113.0 Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.39.0-20251202 Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.39.0-20251202 Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251202 Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251202 Tagged selenium/node-chrome-for-testing:113.0.5672.63-20251202 Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-20251202 Tagged selenium/node-chrome-for-testing:113.0-chromedriver-113.0-grid-4.39.0-20251202 Tagged selenium/standalone-chrome-for-testing:113.0-chromedriver-113.0-grid-4.39.0-20251202 Tagged selenium/node-chrome-for-testing:113.0-chromedriver-113.0-20251202 Tagged selenium/standalone-chrome-for-testing:113.0-chromedriver-113.0-20251202 Tagged selenium/node-chrome-for-testing:113.0-20251202 Tagged selenium/standalone-chrome-for-testing:113.0-20251202 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: Not applicable: Only configuration keys and changelog text were added (e.g., EDGE_VERSION); no new executable code or identifiers were introduced to evaluate naming conventions. Referred Code FIREFOX_PLATFORMS: linux/amd64,linux/arm64 CFT_VERSION: 143.0.7499.42 CHROME_VERSION: google-chrome-stable=143.0.7499.109-1 EDGE_VERSION: microsoft-edge-stable=143.0.3650.80-1 '142': 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: No executable code: The changes are changelog entries and a version update in a YAML matrix without adding runtime logic, so error handling and edge cases cannot be evaluated from the diff. Referred Code ./tag_and_push_browser_images.sh 4.39.0 20251202 selenium false chrome-for-testing true Tagging images for browser chrome-for-testing, version 4.39.0, build date 20251202, namespace selenium Selenium Grid version -> 4.39.0-20251202 Chrome for Testing version -> 140.0.7339.207 Short Chrome for Testing version -> 140.0 ChromeDriver version -> 140.0.7339.207 Short ChromeDriver version -> 140.0 Tagged selenium/node-chrome-for-testing:140.0.7339.207-chromedriver-140.0.7339.207-grid-4.39.0-20251202 Tagged selenium/standalone-chrome-for-testing:140.0.7339.207-chromedriver-140.0.7339.207-grid-4.39.0-20251202 Tagged selenium/node-chrome-for-testing:140.0.7339.207-chromedriver-140.0.7339.207-20251202 Tagged selenium/standalone-chrome-for-testing:140.0.7339.207-chromedriver-140.0.7339.207-20251202 Tagged selenium/node-chrome-for-testing:140.0.7339.207-20251202 Tagged selenium/standalone-chrome-for-testing:140.0.7339.207-20251202 Tagged selenium/node-chrome-for-testing:140.0-chromedriver-140.0-grid-4.39.0-20251202 Tagged selenium/standalone-chrome-for-testing:140.0-chromedriver-140.0-grid-4.39.0-20251202 Tagged selenium/node-chrome-for-testing:140.0-chromedriver-140.0-20251202 Tagged selenium/standalone-chrome-for-testing:140.0-chromedriver-140.0-20251202 Tagged selenium/node-chrome-for-testing:140.0-20251202 Tagged selenium/standalone-chrome-for-testing:140.0-20251202 Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

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

qodo-code-review · 2025-12-12T01:12:49Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Automate changelog generation from structured data Instead of manually committing script outputs as individual changelog files, store version data in a structured format like YAML or JSON. Use this data to automatically generate all necessary documentation during the CI/CD process. Examples: CHANGELOG/4.39.0/chrome-for-testing_113.md [1-21] ./tag_and_push_browser_images.sh 4.39.0 20251202 selenium false chrome-for-testing true Tagging images for browser chrome-for-testing, version 4.39.0, build date 20251202, namespace selenium Selenium Grid version -> 4.39.0-20251202 Chrome for Testing version -> 113.0.5672.63 Short Chrome for Testing version -> 113.0 ChromeDriver version -> 113.0.5672.63 Short ChromeDriver version -> 113.0 Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.39.0-20251202 Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.39.0-20251202 ... (clipped 11 lines) </details> <details> <summary> <a href="https://github.com/SeleniumHQ/docker-selenium/pull/3045/files#diff-b540efd45d2cca1e43fbae8a99a71bf800cf11c10663ef49f43ef3d5484f502dR13-R17">CHANGELOG/README.md [13-17]</a> </summary> ```markdown ### Chrome For Testing \| Grid Version \| 143 \| 142 \| 141 \| 140 \| 139 \| 138 \| 137 \| 136 \| 135 \| 134 \| 133 \| 132 \| 131 \| 130 \| 129 \| 128 \| 127 \| 126 \| 125 \| 124 \| 123 \| 122 \| 121 \| 120 \| 119 \| 118 \| 117 \| 116 \| 115 \| 114 \| 113 \| \|--------------\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\|----\| \| 4.39.0 \| [✓](4.39.0/chrome-for-testing_143.md) \| [✓](4.39.0/chrome-for-testing_142.md) \| [✓](4.39.0/chrome-for-testing_141.md) \| [✓](4.39.0/chrome-for-testing_140.md) \| [✓](4.39.0/chrome-for-testing_139.md) \| [✓](4.39.0/chrome-for-testing_138.md) \| [✓](4.39.0/chrome-for-testing_137.md) \| [✓](4.39.0/chrome-for-testing_136.md) \| [✓](4.39.0/chrome-for-testing_135.md) \| [✓](4.39.0/chrome-for-testing_134.md) \| [✓](4.39.0/chrome-for-testing_133.md) \| [✓](4.39.0/chrome-for-testing_132.md) \| [✓](4.39.0/chrome-for-testing_131.md) \| [✓](4.39.0/chrome-for-testing_130.md) \| [✓](4.39.0/chrome-for-testing_129.md) \| [✓](4.39.0/chrome-for-testing_128.md) \| [✓](4.39.0/chrome-for-testing_127.md) \| [✓](4.39.0/chrome-for-testing_126.md) \| [✓](4.39.0/chrome-for-testing_125.md) \| [✓](4.39.0/chrome-for-testing_124.md) \| [✓](4.39.0/chrome-for-testing_123.md) \| [✓](4.39.0/chrome-for-testing_122.md) \| [✓](4.39.0/chrome-for-testing_121.md) \| [✓](4.39.0/chrome-for-testing_120.md) \| [✓](4.39.0/chrome-for-testing_119.md) \| [✓](4.39.0/chrome-for-testing_118.md) \| [✓](4.39.0/chrome-for-testing_117.md) \| [✓](4.39.0/chrome-for-testing_116.md) \| [✓](4.39.0/chrome-for-testing_115.md) \| [✓](4.39.0/chrome-for-testing_114.md) \| [✓](4.39.0/chrome-for-testing_113.md) \| Solution Walkthrough: Before: // Process: Manually run a script for each version and commit the output. // File: CHANGELOG/4.39.0/chrome-for-testing_113.md ./tag_and_push_browser_images.sh 4.39.0 20251202 ... Tagged selenium/node-chrome-for-testing:113.0... ... `// File: CHANGELOG/4.39.0/chrome-for-testing_114.md` ./tag_and_push_browser_images.sh 4.39.0 20251202 ... Tagged selenium/node-chrome-for-testing:114.0... ... `// ... and 29 more similar files are manually created and committed.` After: # Process: Update a single data file and let CI generate all documentation. # File: data/releases/4.39.0.yml grid_version: 4.39.0 build_date: 20251202 images: - browser: chrome-for-testing version: 113.0.5672.63 driver_version: 113.0.5672.63 - browser: chrome-for-testing version: 114.0.5735.133 driver_version: 114.0.5735.90 # ... all other version info # CI/CD build step (conceptual) # generate_docs.py --from data/releases/4.39.0.yml # This script would create all the .md files and update README.md Suggestion importance[1-10]: 9 __ Why: The suggestion addresses a critical architectural flaw in the documentation process, proposing a scalable and maintainable automated solution that would prevent repository bloat and reduce manual effort.	High
Possible issue	Fix browser and driver version mismatch Align the `ChromeDriver` version with the `Chrome for Testing` version for Chrome 114 to ensure compatibility. CHANGELOG/4.39.0/chrome-for-testing_114.md [5-12] Chrome for Testing version -> 114.0.5735.133 Short Chrome for Testing version -> 114.0 -ChromeDriver version -> 114.0.5735.90 +ChromeDriver version -> 114.0.5735.133 Short ChromeDriver version -> 114.0 -Tagged selenium/node-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.90-grid-4.39.0-20251202 -Tagged selenium/standalone-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.90-grid-4.39.0-20251202 -Tagged selenium/node-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.90-20251202 -Tagged selenium/standalone-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.90-20251202 +Tagged selenium/node-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.133-grid-4.39.0-20251202 +Tagged selenium/standalone-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.133-grid-4.39.0-20251202 +Tagged selenium/node-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.133-20251202 +Tagged selenium/standalone-chrome-for-testing:114.0.5735.133-chromedriver-114.0.5735.133-20251202 Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a version mismatch between the browser and driver for Chrome 114, which could cause compatibility issues for users of the generated Docker images.	Medium
More

…39.0

….39.0

[ci] Upload CHANGELOG for Node/Standalone chrome-for-testing version …

33c0881

…with Grid 4.39.0 Browser versions: [113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143]

qodo-code-review bot added the Review effort 1/5 label Dec 12, 2025

[ci] Upload CHANGELOG for Node/Standalone edge version with Grid 4.39.0

f87f094

selenium-ci added 2 commits December 12, 2025 01:20

[ci] Upload CHANGELOG for Node/Standalone chrome version with Grid 4.…

b2b36ae

…39.0

[ci] Upload CHANGELOG for Node/Standalone firefox version with Grid 4…

3391c45

….39.0

VietND96 merged commit d470460 into trunk Dec 12, 2025
1 check passed

VietND96 deleted the browser-node-changelog branch December 12, 2025 04:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.39.0 #3045

[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.39.0 #3045

Uh oh!

selenium-ci commented Dec 12, 2025 •

edited by qodo-code-review bot

Loading

Uh oh!

qodo-code-review bot commented Dec 12, 2025

Uh oh!

qodo-code-review bot commented Dec 12, 2025

Examples:

Solution Walkthrough:

Before:

After:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.39.0 #3045

[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.39.0 #3045

Uh oh!

Conversation

selenium-ci commented Dec 12, 2025 • edited by qodo-code-review bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

PR Type

Description

Diagram Walkthrough

File Walkthrough

Uh oh!

qodo-code-review bot commented Dec 12, 2025

PR Compliance Guide 🔍

Uh oh!

qodo-code-review bot commented Dec 12, 2025

PR Code Suggestions ✨

Examples:

Solution Walkthrough:

Before:

After:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

selenium-ci commented Dec 12, 2025 •

edited by qodo-code-review bot

Loading