deps: update webdriver-manager requirement from >=4.1.0 to >=4.1.1

[dependabot]

Updates the requirements on webdriver-manager to permit the latest version.

Release notes

Sourced from webdriver-manager's releases.

v4.1.1

4.1.1

This is a focused follow-up release after 4.1.0 to clean up packaging metadata and release documentation.

What’s included

• Fixed README PyPI badges to use webdriver-manager.
• Updated package metadata and version alignment for 4.1.1.
• Standardized release documentation with a new RELEASING.md maintainer runbook.
• Added Python 3.7 CI coverage to reflect the declared support policy.
• Kept packaging behavior stable with a minimal setup.py compatibility shim and pyproject.toml as metadata source-of-truth.

Notes

• No functional driver-resolution changes are included in this release.

Changelog

Sourced from webdriver-manager's changelog.

4.1.1

Packaging

• Fixed package metadata shown on PyPI.
• Added Python version classifiers for currently supported Python versions.
• Removed obsolete universal wheel metadata.
• Ensured release metadata better reflects the current Python support policy.

Docs

• Fixed PyPI badge package name in README.
• Updated README badges to use the published package name webdriver-manager.

Notes

• No functional driver-resolution changes are included in this release.
• This is a packaging and documentation cleanup release following 4.1.0.

---

4.1.0

Compatibility

• Added support for Python 3.12, 3.13, and 3.14.
• Added CI coverage for Python 3.15.0-beta.1.
• Kept compatibility with both Selenium 3 and Selenium 4 usage patterns.
• Improved Chrome / Chromium / Brave support for Chrome 115+ and Chrome for Testing driver resolution.
• Improved Microsoft Edge driver resolution through updated endpoint handling and platform mapping.
• Improved Firefox/geckodriver resolution on Linux ARM64.
• Improved Windows browser version detection through safer PowerShell command execution.
• Improved Docker, CI, and serverless compatibility when default cache locations are unavailable or read-only.

Fixes

• Chrome/Chromium: improved Chrome for Testing resolution and fallbacks for missing exact build metadata, readable errors, and stable URL resolution. (#706, #685, #639)
• Chrome on Windows: prefer win64 on 64-bit hosts with safe fallback to win32 when the win64 asset is unavailable. (#647, #686)
• Edge: updated driver endpoint and improved OS/platform mapping for driver artifacts. (#697)
• Firefox on Linux ARM64: prefer linux-aarch64 geckodriver to avoid architecture mismatch. (#616)
• Windows browser version detection: switched to PowerShell -EncodedCommand flow to avoid quoting and expansion failures in browser version probes. (#625)
• Opera driver install path handling when cache already returns a binary file path, preventing NotADirectoryError caused by directory-only assumptions. (#730)
• Cache reliability: avoid remote version lookup when a valid browser-version cache entry already exists. (#661)
• Cache stability: cache resolved driver version inside the cache manager to reduce repeated metadata and network requests. (#656)
• Concurrency: added an inter-process install lock with post-lock cache recheck to prevent parallel download and unpack races such as BadZipFile and startup failures. (#700, #631)
• Archive extraction robustness: improved zip fallback handling in concurrent or busy-file scenarios.
• Docker/serverless cache path safety: fall back to a writable temp directory when HOME or project-root cache targets are invalid or read-only. (#636, #651, #682, #694)
• Binary selection safety: prevent selecting non-executable companion files such as THIRD_PARTY_NOTICES.* as driver executables. (#667, #670, #683, #699)
• Logger API: set_logger() now accepts logger-like objects exposing log(level, message), not only logging.Logger. (#688)

... (truncated)

Commits

• 179faa0 chore(release): prepare 4.1.1 metadata/docs cleanup and release workflow upda...
• 4af0ce1 chore(security): refresh uv lock for requests and python-dotenv (#733)
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[GeiserX]

LGTM