winget upgrade errors if the CLI is running when we try to update it. We need to exec winget upgrade in the background and then immediately exit. This has the downside that our error handling/messaging isn't as robust, we can't capture timing/success anlytics, and upgrading via the auto-upgrade prompt does not result in running the original command. For ex, if a user runs doppler configs and then chooses to update when prompted, the CLI will update and exit before executing the configs command. We want users to always be on the latest CLI version, so these limitations are preferable to requiring users to manually run doppler update.
winget upgradeerrors if the CLI is running when we try to update it. We need to execwinget upgradein the background and then immediately exit. This has the downside that our error handling/messaging isn't as robust, we can't capture timing/success anlytics, and upgrading via the auto-upgrade prompt does not result in running the original command. For ex, if a user runsdoppler configsand then chooses to update when prompted, the CLI will update and exit before executing theconfigscommand. We want users to always be on the latest CLI version, so these limitations are preferable to requiring users to manually rundoppler update.Closes ENG-6662