Chrome keeps updating, and my bot breaks every few weeks because the web driver is outdated. This is causing significant downtime. Is there a way to automate this update process, or is there a browser designed specifically for automation that doesn't update every second? I need something stable for our production environment.
WebDriverManager libraries automate the process of detecting and downloading the correct driver versions at runtime, ensuring compatibility with updated browser binaries in production environments.
2 answers
You should implement a driver manager utility to handle the synchronization between your browser binary and the executable driver automatically. Instead of manual intervention, integrate a library like WebDriverManager into your CI/CD pipeline or initialization script to detect the version currently installed on the host machine and download the corresponding binary at runtime.
For enterprise-grade stability, rely on headless execution environments that decouple the automation logic from the user-facing interface, as this reduces the frequency of unexpected UI-based failures. While tools like Microsoft Edge or Chrome offer enterprise release channels with long-term support, standardizing your infrastructure via containerization remains the most effective strategy for mitigating version drift across heterogeneous IoT or server nodes.
Stop trying to manage driver files manually because it is a waste of engineering bandwidth. You need to leverage a library that performs binary management on startup or switch your entire stack to Playwright.
Playwright is far superior for production because it ships with its own patched browser binaries, effectively ending the dependency hell between your bot and your local Chrome update cycle.
