docker: bump selenium/standalone-edge from 145.0 to 147.0#9
docker: bump selenium/standalone-edge from 145.0 to 147.0#9dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps selenium/standalone-edge from 145.0 to 147.0. --- updated-dependencies: - dependency-name: selenium/standalone-edge dependency-version: '147.0' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
📝 WalkthroughWalkthroughUpdated the Docker base image from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
![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
🧹 Nitpick comments (1)
Dockerfile (1)
1-1: Use a digest-pinned base image instead of floating tags for reproducible builds.Floating version tags like
:147.0can change if the image is rebuilt, causing unexpected drift in builds. Pin to a digest to ensure the exact same image is always used:-FROM selenium/standalone-edge:147.0 +FROM selenium/standalone-edge:147.0@sha256:<digest>To find the digest:
docker pull selenium/standalone-edge:147.0 && docker inspect --format='{{index .RepoDigests 0}}' selenium/standalone-edge:147.0🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@Dockerfile` at line 1, Replace the floating base image tag in the Dockerfile (the line "FROM selenium/standalone-edge:147.0") with a digest-pinned reference (sha256 digest) so the build is reproducible; obtain the digest by running the suggested commands (docker pull selenium/standalone-edge:147.0 && docker inspect --format='{{index .RepoDigests 0}}' selenium/standalone-edge:147.0) and update the FROM line to use the returned repo@sha256:... value.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@Dockerfile`:
- Line 1: The Dockerfile uses a non-existent image tag
"selenium/standalone-edge:147.0" in its FROM line; change that tag to a
published version such as "selenium/standalone-edge:145.0" (or another available
tag) so the image can be pulled successfully, or hold the current tag until the
official 147.0 release is published and then update the FROM reference
accordingly.
---
Nitpick comments:
In `@Dockerfile`:
- Line 1: Replace the floating base image tag in the Dockerfile (the line "FROM
selenium/standalone-edge:147.0") with a digest-pinned reference (sha256 digest)
so the build is reproducible; obtain the digest by running the suggested
commands (docker pull selenium/standalone-edge:147.0 && docker inspect
--format='{{index .RepoDigests 0}}' selenium/standalone-edge:147.0) and update
the FROM line to use the returned repo@sha256:... value.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| @@ -1,4 +1,4 @@ | |||
| FROM selenium/standalone-edge:145.0 | |||
| FROM selenium/standalone-edge:147.0 | |||
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Selenium standalone-edge 147.0 release notes and breaking changes
💡 Result:
No official Selenium standalone-edge Docker image tagged with exactly "147.0" exists as of 2026-04-13. The highest Edge version available is 145.0 (tags like selenium/standalone-edge:145.0-20260222, 145.0-edgedriver-145.0-grid-4.41.0-20260222). Current nightly images use Edge 146.0.3856.97. Microsoft Edge 147 (e.g., 147.0.3912.60 stable as of April 10, 2026) and matching EdgeDriver (beta/dev channels) are available, but no corresponding Selenium Docker release notes or images for 147.0 have been published yet. Selenium Grid 4.41.0 supports CDP v143-v145, with no specific mention of Edge 147 compatibility or breaking changes.
Citations:
- 1: https://github.com/seleniumhq/docker-selenium/releases
- 2: https://hub.docker.com/r/selenium/standalone-edge/tags
- 3: https://github.com/SeleniumHQ/docker-selenium/releases/tag/nightly
- 4: https://www.selenium.dev/blog/2026/selenium-grid-4-41-deep-dive/
- 5: https://raw.githubusercontent.com/SeleniumHQ/selenium/master/java/CHANGELOG
- 6: https://github.com/SeleniumHQ/docker-selenium/tree/trunk/CHANGELOG
- 7: https://github.com/SeleniumHQ/docker-selenium/releases
🌐 Web query:
Selenium Python 4.43.0 compatibility with Microsoft Edge 147 WebDriver
💡 Result:
Yes, Selenium Python 4.43.0 is compatible with Microsoft Edge version 147 using the corresponding msedgedriver.
Citations:
- 1: https://selenium-python-api-docs.readthedocs.io/en/selenium-4.43.0/
- 2: https://www.selenium.dev/selenium/docs/api/py/selenium_webdriver_edge/selenium.webdriver.edge.webdriver.html
- 3: https://pypi.org/project/selenium/
- 4: https://developer.microsoft.com/microsoft-edge/tools/webdriver/
- 5: https://www.selenium.dev/documentation/webdriver/browsers/
- 6: https://github.com/SeleniumHQ/selenium/blob/trunk/py/CHANGES
Docker image selenium/standalone-edge:147.0 does not exist.
The tag is not published in the Selenium Docker registry as of April 2026. The highest available version is 145.0. Use selenium/standalone-edge:145.0 or wait for the official 147.0 release. Selenium Python 4.43.0 is compatible with Edge 147, so version alignment is not a concern once a valid image tag is available.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@Dockerfile` at line 1, The Dockerfile uses a non-existent image tag
"selenium/standalone-edge:147.0" in its FROM line; change that tag to a
published version such as "selenium/standalone-edge:145.0" (or another available
tag) so the image can be pulled successfully, or hold the current tag until the
official 147.0 release is published and then update the FROM reference
accordingly.
1 participant
Bumps selenium/standalone-edge from 145.0 to 147.0.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit