SeleniumHQ / SeleniumHQ/docker-selenium
[🚀 Feature]: Request to upgrade Libcurl to match curl version
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
Feature and motivation
Hello Team,
Currently in our organization we are using latest image 4.34.0-20250717 for node images. Libcurl version for latest image is still in v8.5 even though curl is upgraded to v8.11. It seems the Libcurl version taking from the interdependent package. According to security scanning it is expected to use Libcurl v8.11 or greater.
Could you please let us know if you are going to fix that in upcoming versions.
Thank you!
Usage example
Not Applicable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue targets the node image version 4.34.0-20250717 and its curl/libcurl package versions; start by locating how that image obtains the interdependent libcurl package. Done means a rebuilt image reports libcurl v8.11 or newer while retaining the requested curl version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100