Update selenium/standalone-chromium Docker tag to v147#163
Update selenium/standalone-chromium Docker tag to v147#163AlexSkrypnyk merged 1 commit intodevelopfrom
Conversation
AlexSkrypnyk
added
the
Dependencies
📝 WalkthroughWalkthroughUpdated the Docker image tag for the Chrome Selenium service in docker-compose.yml from version 145.0 to 147.0, changing the Chromium browser testing environment without altering any other service configurations or dependencies. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 the current code and only fix it if needed.
Inline comments:
In `@docker-compose.yml`:
- Line 204: Replace the non-existent image tag in the docker-compose service
(the line with image: selenium/standalone-chromium:147.0) with the published tag
selenium/standalone-chromium:145.0 so the compose file pulls a valid Docker
image; update any related documentation or comments referencing 147.0 to reflect
the reverted 145.0 tag.
🪄 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
Run ID: bd342b9f-7fd5-4e7a-8f9d-bb48e142b818
📒 Files selected for processing (1)
docker-compose.yml
| # Chrome container, used for browser testing. | ||
| chrome: | ||
| image: selenium/standalone-chromium:145.0 | ||
| image: selenium/standalone-chromium:147.0 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify the selenium/standalone-chromium:147.0 image exists and check for security advisories
# Verify image exists on Docker Hub
echo "Checking if selenium/standalone-chromium:147.0 exists on Docker Hub..."
curl -s "https://hub.docker.com/v2/repositories/selenium/standalone-chromium/tags/147.0" | jq -r '.name // "Image not found"'
# Check for security advisories using GitHub advisory database
echo -e "\nChecking for security advisories..."
gh api graphql -f query='
{
securityVulnerabilities(first: 10, ecosystem: DOCKER, package: "selenium/standalone-chromium") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'Repository: drevops/website
Length of output: 333
🌐 Web query:
selenium standalone-chromium version 147.0 release notes breaking changes
💡 Result:
No official selenium/standalone-chromium image tagged with version 147.0 exists as of 2026-04-13. Docker Hub tags show the highest Chromium version is 145.0 (e.g., selenium/standalone-chromium:145.0-chromedriver-145.0-grid-4.41.0-20260222 from Selenium docker-selenium release 4.41.0-20260222). Recent releases use Chromium 145.0.7632.109, Chrome 145.0.7632.116, with Firefox at 147.0.4 (note: Firefox 147, not Chromium). Chromium 147 stable released April 7, 2026, but Selenium images lag behind Chrome stable schedule. No release notes or changelog for a 147.0 image found in docker-selenium GitHub releases, CHANGELOGs, or Docker Hub. No breaking changes documented because no such image exists. Use nightly tag for latest (Chromium <147) or wait for future release. Chrome 147 release notes available separately but unrelated to Selenium Standalone.
Citations:
- 1: https://hub.docker.com/r/selenium/standalone-chromium
- 2: https://github.com/seleniumhq/docker-selenium/releases
- 3: https://hub.docker.com/r/selenium/standalone-chromium/tags
- 4: https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.41.0-20260222
- 5: https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.40.0-20260202
- 6: https://www.selenium.dev/blog/2026/selenium-grid-4-41-deep-dive/
Revert to selenium/standalone-chromium:145.0 — the 147.0 image does not exist.
The image tag selenium/standalone-chromium:147.0 is not available on Docker Hub. As of April 2026, the latest available version is 145.0. While Chromium 147 was released on April 7, 2026, Selenium's docker-selenium project has not yet published official builds for it. Using this non-existent tag will cause image pull failures when running the containers.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docker-compose.yml` at line 204, Replace the non-existent image tag in the
docker-compose service (the line with image: selenium/standalone-chromium:147.0)
with the published tag selenium/standalone-chromium:145.0 so the compose file
pulls a valid Docker image; update any related documentation or comments
referencing 147.0 to reflect the reverted 145.0 tag.
|
Code coverage (GitHub Actions) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #163 +/- ##
========================================
Coverage 87.73% 87.73%
========================================
Files 11 11
Lines 163 163
========================================
Hits 143 143
Misses 20 20 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
This PR contains the following updates:
145.0→147.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 Renovate Bot.