## What this fixes
If a local environment variable has the same name as a Doppler secret, `doppler run` picks the local value instead of the Doppler one, even without the --preserve-env flag. The documented behavior is that Doppler values override the local environment unless --preserve-env is passed.
## The fix
This was a CLI regression the Doppler team confirmed and fixed, the fix shipped in v3.19.1 with new regression tests. Upgrade to v3.19.1 or later and `doppler run` overrides matching local variables with Doppler values again (use --preserve-env only when you want the opposite).
Source: https://github.com/DopplerHQ/cli/issues/307
## Why it happens
The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.
## Source
https://github.com/DopplerHQ/cli/issues/307