Bound environment variables get written to disk

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.
[X] I have checked the troubleshooting guide for my problem, without success.

Viper Version

1.19.0

Go Version

1.22.5

Config Source

Flags, Environment variables, Files

Format

JSON

Repl.it link

https://replit.com/@darrellwarde/Viper-example

Code reproducing the issue

No response

Expected Behavior

Upon writing config files, I would expect that only the following configuration values would be written to disk:

Default configuration values
Values already set in the configuration file
Values explicitly set using Viper.Set()

Actual Behavior

Configuration values from mapped environment variables get written to configuration file if they have values whilst writing config files. This is unexpected because you generally only expect environment variables to effect the behaviour of executions for which they are set, but because of this, they will be persisted to disk and still act as the configuration values when the variables are no longer set.

In the Repl.it, use the shell to set YEARS_SINCE_BORN during execution. Even though age is never explicitly set in the config, it gets written to the config file purely from the environment variable being set during execution.

Steps To Reproduce

No response

Additional Information

No response

spf13 / viper