[ci] CHANGELOG for Node/Standalone browser versions with Grid 4.38.0

[selenium-ci]

User description

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

---

PR Type

Documentation

---

Description

• Add Chrome for Testing version 142 changelog entries

• Extend browser version support to include version 142

• Update Edge version configuration for version 142

• Expand release workflow default browser versions list

---

Diagram Walkthrough

flowchart LR
  A["Release Workflow"] -->|"Add version 142"| B["Browser Versions List"]
  C["Chrome for Testing v113-v141"] -->|"Extend to v142"| D["Chrome for Testing v113-v142"]
  E["Browser Matrix Config"] -->|"Add Edge v142"| F["Updated Matrix"]
  D --> G["30 Changelog Files"]
  B --> H["Updated Default Versions"]

Loading

File Walkthrough

	Relevant files
Configuration changes	2 files release-edge-versions.yml Extend default browser versions to include 142                      +1/-1      browser-matrix.yml Add Edge version 142 to browser matrix configuration          +1/-0
Documentation	30 files chrome-for-testing_113.md Add Chrome for Testing v113 build changelog                            +21/-0    chrome-for-testing_114.md Add Chrome for Testing v114 build changelog                            +21/-0    chrome-for-testing_115.md Add Chrome for Testing v115 build changelog                            +21/-0    chrome-for-testing_116.md Add Chrome for Testing v116 build changelog                            +21/-0    chrome-for-testing_117.md Add Chrome for Testing v117 build changelog                            +21/-0    chrome-for-testing_118.md Add Chrome for Testing v118 build changelog                            +21/-0    chrome-for-testing_119.md Add Chrome for Testing v119 build changelog                            +21/-0    chrome-for-testing_120.md Add Chrome for Testing v120 build changelog                            +21/-0    chrome-for-testing_121.md Add Chrome for Testing v121 build changelog                            +21/-0    chrome-for-testing_122.md Add Chrome for Testing v122 build changelog                            +21/-0    chrome-for-testing_123.md Add Chrome for Testing v123 build changelog                            +21/-0    chrome-for-testing_124.md Add Chrome for Testing v124 build changelog                            +21/-0    chrome-for-testing_125.md Add Chrome for Testing v125 build changelog                            +21/-0    chrome-for-testing_126.md Add Chrome for Testing v126 build changelog                            +21/-0    chrome-for-testing_127.md Add Chrome for Testing v127 build changelog                            +21/-0    chrome-for-testing_128.md Add Chrome for Testing v128 build changelog                            +21/-0    chrome-for-testing_129.md Add Chrome for Testing v129 build changelog                            +21/-0    chrome-for-testing_130.md Add Chrome for Testing v130 build changelog                            +21/-0    chrome-for-testing_131.md Add Chrome for Testing v131 build changelog                            +21/-0    chrome-for-testing_132.md Add Chrome for Testing v132 build changelog                            +21/-0    chrome-for-testing_133.md Add Chrome for Testing v133 build changelog                            +21/-0    chrome-for-testing_134.md Add Chrome for Testing v134 build changelog                            +21/-0    chrome-for-testing_135.md Add Chrome for Testing v135 build changelog                            +21/-0    chrome-for-testing_136.md Add Chrome for Testing v136 build changelog                            +21/-0    chrome-for-testing_137.md Add Chrome for Testing v137 build changelog                            +21/-0    chrome-for-testing_138.md Add Chrome for Testing v138 build changelog                            +21/-0    chrome-for-testing_139.md Add Chrome for Testing v139 build changelog                            +21/-0    chrome-for-testing_140.md Add Chrome for Testing v140 build changelog                            +21/-0    chrome-for-testing_141.md Add Chrome for Testing v141 build changelog                            +21/-0    chrome-for-testing_142.md Add Chrome for Testing v142 build changelog                            +21/-0

---

[qodo-merge-pro]

PR Compliance Guide 🔍

(Compliance updated until commit bc07d9e)

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: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	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
	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
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Non-applicable Scope: The PR adds configuration and changelog documentation without implementing runtime actions requiring audit logging; no critical actions are introduced that would necessitate audit trails. Referred Code default: '[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]' push-image:
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error paths: The new changes only expand default version lists and add changelog entries, introducing no executable error-prone logic within the diff to evaluate for error handling. Referred Code default: '[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]' push-image:
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: External inputs: The changes update version strings in configuration without introducing new external input handling code, so validation and sanitization cannot be assessed from this diff alone. Referred Code matrix: browser: '144': FIREFOX_VERSION: 144.0.2 FIREFOX_PLATFORMS: linux/amd64,linux/arm64 '143': FIREFOX_VERSION: 143.0.4 FIREFOX_PLATFORMS: linux/amd64,linux/arm64 '142': FIREFOX_VERSION: 142.0.1 FIREFOX_PLATFORMS: linux/amd64,linux/arm64 CHROME_VERSION: google-chrome-stable=142.0.7444.59-1 CFT_VERSION: 142.0.7444.59 EDGE_VERSION: microsoft-edge-stable=142.0.3595.53-1 '141': EDGE_VERSION: microsoft-edge-stable=141.0.3537.99-1 CHROME_VERSION: google-chrome-stable=141.0.7390.122-1 FIREFOX_VERSION: 141.0.3

Compliance status legend

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

---

Previous compliance checks

Compliance check up to commit 2336fca

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: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	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
	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
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit logs: The new workflow default list change on line 34 does not include any added logging of critical actions, but this PR appears to be documentation/config only and may not require audit trails. Referred Code default: '[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]' push-image:
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error handling: The added default browser versions value on line 34 introduces configuration without accompanying failure handling or validation in this diff, though such handling may exist elsewhere in the workflow. Referred Code default: '[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]' push-image:
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Input validation: The newly added EDGE_VERSION for version '142' (line 14) is configuration that could affect builds but the diff shows no validation or checksum/pinning beyond package versioning, which may be handled elsewhere. Referred Code EDGE_VERSION: microsoft-edge-stable=142.0.3595.53-1 '141':

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Fix malformed Docker image tags Suggestion Impact: The commit updates the changelog to include proper Chrome for Testing and ChromeDriver versions and corrects the resulting Docker image tags, replacing the previously empty/malformed values. code diff: -Chrome for Testing version -> -Short Chrome for Testing version -> . -ChromeDriver version -> -Short ChromeDriver version -> . -Tagged selenium/node-chrome-for-testing:-chromedriver--grid-4.38.0-20251025 -Tagged selenium/standalone-chrome-for-testing:-chromedriver--grid-4.38.0-20251025 -Tagged selenium/node-chrome-for-testing:-chromedriver--20251025 -Tagged selenium/standalone-chrome-for-testing:-chromedriver--20251025 -Tagged selenium/node-chrome-for-testing:-20251025 -Tagged selenium/standalone-chrome-for-testing:-20251025 -Tagged selenium/node-chrome-for-testing:.-chromedriver-.-grid-4.38.0-20251025 -Tagged selenium/standalone-chrome-for-testing:.-chromedriver-.-grid-4.38.0-20251025 -Tagged selenium/node-chrome-for-testing:.-chromedriver-.-20251025 -Tagged selenium/standalone-chrome-for-testing:.-chromedriver-.-20251025 -Tagged selenium/node-chrome-for-testing:.-20251025 -Tagged selenium/standalone-chrome-for-testing:.-20251025 +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.38.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.38.0-20251025 +Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251025 +Tagged selenium/node-chrome-for-testing:113.0.5672.63-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-20251025 +Tagged selenium/node-chrome-for-testing:113.0-chromedriver-113.0-grid-4.38.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0-chromedriver-113.0-grid-4.38.0-20251025 +Tagged selenium/node-chrome-for-testing:113.0-chromedriver-113.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0-chromedriver-113.0-20251025 +Tagged selenium/node-chrome-for-testing:113.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0-20251025 Fix the malformed Docker image tags in the newly added chrome-for-testing_*.md files. The script output shows a failure to retrieve Chrome and ChromeDriver versions, which needs to be corrected. CHANGELOG/4.38.0/chrome-for-testing_113.md [1-21] ./tag_and_push_browser_images.sh 4.38.0 20251025 selenium false chrome-for-testing true Tagging images for browser chrome-for-testing, version 4.38.0, build date 20251025, namespace selenium Selenium Grid version -> 4.38.0-20251025 -Chrome for Testing version -> -Short Chrome for Testing version -> . -ChromeDriver version -> -Short ChromeDriver version -> . -Tagged selenium/node-chrome-for-testing:-chromedriver--grid-4.38.0-20251025 -Tagged selenium/standalone-chrome-for-testing:-chromedriver--grid-4.38.0-20251025 -Tagged selenium/node-chrome-for-testing:-chromedriver--20251025 -Tagged selenium/standalone-chrome-for-testing:-chromedriver--20251025 -Tagged selenium/node-chrome-for-testing:-20251025 -Tagged selenium/standalone-chrome-for-testing:-20251025 -Tagged selenium/node-chrome-for-testing:.-chromedriver-.-grid-4.38.0-20251025 -Tagged selenium/standalone-chrome-for-testing:.-chromedriver-.-grid-4.38.0-20251025 -Tagged selenium/node-chrome-for-testing:.-chromedriver-.-20251025 -Tagged selenium/standalone-chrome-for-testing:.-chromedriver-.-20251025 -Tagged selenium/node-chrome-for-testing:.-20251025 -Tagged selenium/standalone-chrome-for-testing:.-20251025 +Chrome for Testing version -> 113.0.5672.63 +Short Chrome for Testing version -> 113 +ChromeDriver version -> 113.0.5672.63 +Short ChromeDriver version -> 113 +Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.38.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-grid-4.38.0-20251025 +Tagged selenium/node-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-chromedriver-113.0.5672.63-20251025 +Tagged selenium/node-chrome-for-testing:113.0.5672.63-20251025 +Tagged selenium/standalone-chrome-for-testing:113.0.5672.63-20251025 +Tagged selenium/node-chrome-for-testing:113-chromedriver-113-grid-4.38.0-20251025 +Tagged selenium/standalone-chrome-for-testing:113-chromedriver-113-grid-4.38.0-20251025 +Tagged selenium/node-chrome-for-testing:113-chromedriver-113-20251025 +Tagged selenium/standalone-chrome-for-testing:113-chromedriver-113-20251025 +Tagged selenium/node-chrome-for-testing:113-20251025 +Tagged selenium/standalone-chrome-for-testing:113-20251025 [Suggestion processed] Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical issue where all new changelog files contain malformed Docker tags due to a script failure, rendering the primary contribution of this PR incorrect.	High
More