Hello! This change has a side effect that the .env file is prioritized over the exported environment, this breaks our docker compose (and other) flows, where the .env file is loaded and then overrided with env: values.

Was this an intentional change?

Originally posted by @DougEdey-Slice in #393

This was an unintentional breaking change. Previously, we were delegating to python-dotenv's os.environ.setdefault(key, value) behavior. #462 switched the order of precedence.