Update selenium/standalone-chromium Docker tag to v149#233
Conversation
| datasource | package | from | to | | ---------- | ---------------------------- | ----- | ----- | | docker | selenium/standalone-chromium | 148.0 | 149.0 |
AlexSkrypnyk
added
the
Dependencies
📝 WalkthroughWalkthroughThe ChangesChromium Image Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docker-compose.yml`:
- Line 204: The selenium/standalone-chromium image reference at line 204 uses an
invalid tag format `149.0`. The Docker Hub selenium/standalone-chromium
repository requires tags in the format `<Major>.<Minor>.<Patch>-<YYYYMMDD>`
(e.g., `4.44.0-20260505`). Replace the current image tag with a valid Selenium
Grid version tag from the Docker Hub repository, or if you specifically need
Chromium 149.0, update the image reference to use
`selenium/standalone-chrome-for-testing:149.0-<YYYYMMDD>` instead, where the
date portion matches an available tag on Docker Hub.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: fa58694c-8eee-4f91-b26b-b1cae6f86fad
📒 Files selected for processing (1)
docker-compose.yml
| # Chrome container, used for browser testing. | ||
| chrome: | ||
| image: selenium/standalone-chromium:148.0 | ||
| image: selenium/standalone-chromium:149.0 |
There was a problem hiding this comment.
🩺 Stability & Availability | 🔴 Critical
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify selenium/standalone-chromium:149.0 image availability and check release info
# Check if the Docker image exists and is pullable
echo "Checking Docker image availability..."
docker manifest inspect selenium/standalone-chromium:149.0 > /dev/null 2>&1
if [ $? -eq 0 ]; then
echo "✓ Image selenium/standalone-chromium:149.0 exists"
docker manifest inspect selenium/standalone-chromium:149.0 | jq -r '.manifests[0].platform | "Platform: \(.os)/\(.architecture)"'
else
echo "✗ Image selenium/standalone-chromium:149.0 not found"
fi
# Check for recent issues or discussions about version 149.0
echo -e "\nSearching for selenium-docker issues related to version 149..."
gh api graphql -f query='
{
search(query: "repo:SeleniumHQ/docker-selenium 149 in:title,body", type: ISSUE, first: 5) {
nodes {
... on Issue {
title
url
state
createdAt
}
... on PullRequest {
title
url
state
createdAt
}
}
}
}'Repository: drevops/website
Length of output: 1439
🏁 Script executed:
#!/bin/bash
# Description: Run tests with the new Chromium version
# Pull the new image
docker compose pull chrome
# Run your test suite (adjust command as needed for your project)
docker compose up -d chrome
# Add your actual test command here, e.g.:
# docker compose run --rm cli npm test
# docker compose run --rm cli pytest tests/Repository: drevops/website
Length of output: 237
🌐 Web query:
selenium/standalone-chromium:149.0 Docker Hub availability
💡 Result:
selenium/standalone-chromium:149.0 does not appear to be available on Docker Hub as of 2026-06-23, while other 149.x and 148.x tags are shown. Evidence: the official Docker Hub “Tags for selenium/standalone-chromium” page lists many tags (example shown include 148.0 and 147.0), but the provided tag listing in the source does not show a 149.0 tag entry; instead it highlights other version patterns such as 148.0 and 147.0 and includes Chrome-for-testing 149.0-* tags under a different repository (selenium/standalone-chrome-for-testing). [1][2] Practical takeaway: if you need Chromium/Chrome 149 in the Selenium standalone-chromium image, check the exact tag names from the official tags page (likely 149.0-<YYYYMMDD> or 149.0-chromedriver-149.0-<YYYYMMDD> style tags). [1][3]
Citations:
- 1: https://hub.docker.com/r/selenium/standalone-chromium/tags
- 2: https://hub.docker.com/r/selenium/standalone-chrome-for-testing/tags
- 3: https://hub.docker.com/r/selenium/standalone-chromium
🌐 Web query:
Chromium 149.0 release notes breaking changes
💡 Result:
Chromium 149, which reached its stable release on June 2, 2026, included several notable changes, though official release documentation does not label them as traditional "breaking changes" in terms of major API deprecations [1]. Instead, the release focused on feature enhancements and behavioral adjustments [1][2]. Key updates and adjustments in Chromium 149 include: CSS and UI Enhancements: - Introduced CSS gap decorations, allowing for styling of gaps in grid and flexbox layouts using properties like column-rule-inset and row-rule-inset [1][2]. - Implemented temporary switching of text overflow from ellipsis to clip during user interaction (such as editing or caret navigation) to improve visibility [1]. - Removed the explicit border color rule for tables from the user-agent stylesheet to address potential rendering or accessibility issues [1]. - Added support for path, shape, rect, and xywh within the shape-outside property [1]. Network and Connectivity: - Active WebSocket connections no longer prevent pages from entering the Back/Forward Cache (bfcache) [1][2]. The browser now proactively closes WebSocket connections on bfcache entry rather than marking the document as ineligible for caching [1][2]. Developer Tools: - DevTools introduced experimental WebMCP (Web Model Context Protocol) debugging tools within the Application panel [3]. - The Advanced Perceptual Contrast Algorithm (APCA) calculator moved out of its experimental phase to become a standard preference setting [3]. - Code completion support in the Styles tab was expanded to include Gemini-powered suggestions [3]. For developers, it is recommended to review the full developer release notes and the "New in Chrome 149" blog post for exhaustive details on these updates, as specific implementations or refinements may affect site-specific styling or network behaviors [1][2]. The release was part of the standard versioning cadence, and Chromium continues to transition toward a two-week release cycle, which is scheduled to take full effect starting with Chrome 153 in September 2026 [4][5].
Citations:
- 1: https://developer.chrome.com/release-notes/149
- 2: https://developer.chrome.com/blog/new-in-chrome-149
- 3: https://developer.chrome.com/blog/new-in-devtools-149
- 4: https://www.securityweek.com/google-plans-two-week-release-schedule-for-chrome/
- 5: https://developer.chrome.com/blog/chrome-two-week-release
🏁 Script executed:
#!/bin/bash
# Check docker-compose.yml to understand the full context of this image
cd /tmp && git clone --depth 1 https://github.com/drevops/website.git 2>/dev/null || cd website
head -n 250 docker-compose.yml | tail -n 60Repository: drevops/website
Length of output: 231
🏁 Script executed:
#!/bin/bash
# Find docker-compose.yml in the repository
find . -name "docker-compose.yml" -type f 2>/dev/null | head -20Repository: drevops/website
Length of output: 174
🏁 Script executed:
#!/bin/bash
# Check the actual docker-compose.yml content around line 204
find . -name "docker-compose.yml" -type f -exec grep -n "selenium/standalone-chromium" {} + 2>/dev/nullRepository: drevops/website
Length of output: 203
🌐 Web query:
selenium/standalone-chromium available Docker Hub tags versions 2026
💡 Result:
As of June 2026, the selenium/standalone-chromium image on Docker Hub continues to follow a standardized tagging convention that includes browser versions, driver versions, Selenium Grid versions, and a build timestamp [1]. For the year 2026, tags are structured as follows: - Pinned releases: selenium/standalone-chromium:..- [1] - Detailed versioning: selenium/standalone-chromium:---..- [1] - General tags: You can also use tags such as latest, nightly, or shorter versions like 4 or 4.44 [2][1]. Examples of tags released in 2026 include: - 4.44.0-20260505 [2] - 4.43.0-20260404 [3] - 4.40.0-20260202 [4] To ensure stability in production environments, it is recommended to use the full pinned tags rather than latest [1]. Additionally, please note that as of April 2026, official Selenium Grid Docker images are also mirrored to the GitHub Container Registry (GHCR) under the ghcr.io/seleniumhq namespace, providing an alternative to Docker Hub [5].
Citations:
- 1: https://hub.docker.com/r/selenium/standalone-chromium
- 2: https://hub.docker.com/r/selenium/standalone-chromium/tags
- 3: https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.43.0-20260404
- 4: https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.40.0-20260202
- 5: https://www.selenium.dev/blog/2026/selenium-grid-docker-images-are-now-mirrored-to-ghcr/
The tag selenium/standalone-chromium:149.0 does not exist on Docker Hub and will fail at runtime.
The selenium/standalone-chromium image on Docker Hub does not use simple version tags like 149.0. Valid tags follow the format <Major>.<Minor>.<Patch>-<YYYYMMDD> (e.g., 4.44.0-20260505). The number 149.0 refers to the Chromium version, not the Selenium Grid version.
Update the image reference to a valid tag from the selenium/standalone-chromium repository, or use selenium/standalone-chrome-for-testing:149.0-<YYYYMMDD> if you specifically need Chromium 149.0 with the Chrome for Testing variant.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docker-compose.yml` at line 204, The selenium/standalone-chromium image
reference at line 204 uses an invalid tag format `149.0`. The Docker Hub
selenium/standalone-chromium repository requires tags in the format
`<Major>.<Minor>.<Patch>-<YYYYMMDD>` (e.g., `4.44.0-20260505`). Replace the
current image tag with a valid Selenium Grid version tag from the Docker Hub
repository, or if you specifically need Chromium 149.0, update the image
reference to use `selenium/standalone-chrome-for-testing:149.0-<YYYYMMDD>`
instead, where the date portion matches an available tag on Docker Hub.
|
Code coverage (threshold: 80%) Per-class coverage |
1 participant
This PR contains the following updates:
148.0→149.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (in timezone Australia/Melbourne)
🚦 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.
This PR has been generated by Mend Renovate.
Summary by CodeRabbit