Skip to content

Update selenium/standalone-chromium Docker tag to v147 #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexSkrypnyk merged 1 commit into from
Apr 14, 2026
Merged

Update selenium/standalone-chromium Docker tag to v147 #163

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,7 @@ services:

# Chrome container, used for browser testing.
chrome:
image: selenium/standalone-chromium:145.0
image: selenium/standalone-chromium:147.0
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 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:

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.

environment:
<<: *default-environment
<<: *default-volumes
Expand Down
Loading