Skip to content

Update selenium/standalone-chromium Docker tag to v149#2706

Open
AlexSkrypnyk wants to merge 1 commit into
mainfrom
deps/selenium-standalone-chromium-149.x
Open

Update selenium/standalone-chromium Docker tag to v149#2706
AlexSkrypnyk wants to merge 1 commit into
mainfrom
deps/selenium-standalone-chromium-149.x

Conversation

@AlexSkrypnyk

@AlexSkrypnyk AlexSkrypnyk commented Jun 23, 2026

Copy link
Copy Markdown
Member

This PR contains the following updates:

Package Update Change
selenium/standalone-chromium major 148.0149.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

Summary by CodeRabbit

  • Chores
    • Updated browser testing infrastructure to use the latest version of testing tools, ensuring compatibility testing remains current with the latest browser standards.

| datasource | package                      | from  | to    |
| ---------- | ---------------------------- | ----- | ----- |
| docker     | selenium/standalone-chromium | 148.0 | 149.0 |
@AlexSkrypnyk AlexSkrypnyk added the Dependencies Pull request was raised automatically by a dependency bot label Jun 23, 2026
@github-project-automation github-project-automation Bot moved this to BACKLOG in Vortex 1.x Jun 23, 2026
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5135b2b6-00a9-4e30-81de-08c99f06f49f

📥 Commits

Reviewing files that changed from the base of the PR and between 12ce7b8 and 0c22ee3.

📒 Files selected for processing (1)
  • docker-compose.yml

Walkthrough

The chrome service in docker-compose.yml has its container image tag updated from selenium/standalone-chromium:148.0 to selenium/standalone-chromium:149.0. No other configuration is changed.

Changes

Chrome Image Version Bump

Layer / File(s) Summary
Chrome service image tag update
docker-compose.yml
The chrome service image is bumped from selenium/standalone-chromium:148.0 to selenium/standalone-chromium:149.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐇 A single line changed, oh what a day,
The chromium hopped from 148's way,
Now 149 runs in the docker nest,
A tiny bump to keep our browsers blessed,
Hippity-hop, the tests shall play! 🎉

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: updating the selenium/standalone-chromium Docker image tag from 148.0 to 149.0.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch deps/selenium-standalone-chromium-149.x

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.58% (208/211)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

Copy link
Copy Markdown
Member Author

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.58% (208/211)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@github-actions

Copy link
Copy Markdown

📖 Documentation preview for this pull request has been deployed to Netlify:

https://6a3a820e77edc19811e4d51a--vortex-docs.netlify.app

This preview is rebuilt on every commit and is not the production documentation site.

@codecov

codecov Bot commented Jun 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.22%. Comparing base (12ce7b8) to head (0c22ee3).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2706      +/-   ##
==========================================
- Coverage   86.67%   86.22%   -0.45%     
==========================================
  Files          96       89       -7     
  Lines        4719     4560     -159     
  Branches       47        3      -44     
==========================================
- Hits         4090     3932     -158     
+ Misses        629      628       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dependencies Pull request was raised automatically by a dependency bot

Projects

Status: BACKLOG

Development

Successfully merging this pull request may close these issues.

1 participant