mise add warning about migration

[ev-dev]

• Adds warning message about manual config migration.
• Update to version 2025.1.13

[github-actions]

All changes look good.

Wait for review from human collaborators.

mise

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[ev-dev]

I'll look into scripting a migration of previous mise installs, but it may not be necessary. Is a warning message alone an acceptable UX?

[stevehipwell]

@ev-dev it'd be best if scoop didn't modify existing mise configuration, the install script could check for non-scoop values in the env. See #6477.

[ev-dev]

Indeed, I agree @stevehipwell this PR simply adds the warning message:

This manifest does not currently migrate any previous mise installations!

Suggested:

• Backup existing config.toml before fully uninstalling mise as documented.
• Install with scoop then manually add the backed up options to the new config.toml that scoop now manages in persist

My thought was that the best way to ovoid an install conflict with previous installs, would be to have a clean install with scoop. I figured this message would at least be better than not addressing or mentioning previous installs no?

[stevehipwell]

The whole mise Scoop installation breaks existing configuration, the warning message doesn't really deal with that as it suggest that the intended behaviour is to replace the existing env variables and paths. The best solution would be to use an install script to detect if mise has been configured already to point outside the Scoop dir and if so not change anything related to that.