Selenium Manager and Browser Driver Compatibility: Fallback Behavior When No Matching Driver Exists

The goal is to achieve a repeatable development environment where Selenium Manager automatically supplies the correct browser driver for the installed Selenium version, ensuring consistent test execution across CI pipelines.

An unresolved uncertainty arises when Selenium Manager encounters a browser version newer than any available driver: it currently falls back to the last known compatible driver. This fallback can mask version mismatches and lead to flaky test results, yet the official documentation does not prescribe whether the manager should error, warn, or require explicit version pinning in such cases.

Should Selenium Manager default to failing fast when no exact driver match exists? Should it emit a warning and continue with the fallback? Should teams be advised to pin driver versions explicitly in their build scripts to avoid the fallback behavior?