[bug] cargo tauri migrate doesn't migrate tauri.conf.json

[kornelski]

Describe the bug

I have a Tauri project that stopped working after 2.0.0-alpha.8

I'm trying to revive it, but to my great disappointment, cargo tauri migrate doesn't seem to do anything. It doesn't output anything at all by default. It doesn't modify any files. It doesn't report any problems. It doesn't report any incompatibilities.

It doesn't update tauri.conf.json to whatever new structure it's supposed to have, which leaves Tauri completely unusable.

cargo tauri migrate --verbose prints Debug [tauri_cli::helpers::app_paths] Found Tauri project inside ... and debug about gitignore (the conf file isn't ignored).

Reproduction

Clone https://gitlab.com/kornelski/gifski-win/-/tree/tauri-migrate-flop
and run cargo tauri migrate

cargo tauri migrate
cargo tauri dev
       Error `tauri.conf.json` error: "identifier" is a required property
       Error `tauri.conf.json` error on `build`: Additional properties are not allowed ('devPath', 'distDir', 'withGlobalTauri' were unexpected)
       Error `tauri.conf.json` error: Additional properties are not allowed ('package', 'tauri' were unexpected)

Expected behavior

I hope it would understand the config from all previous versions, and fix it to work with the latest version.

OR at least print an error message that this config format is dead and abandoned. Printing nothing at all while failing to migrate, looks like a bug.

Full tauri info output

cargo tauri info
       Error `tauri.conf.json` error: "identifier" is a required property
       Error `tauri.conf.json` error on `build`: Additional properties are not allowed ('devPath', 'distDir', 'withGlobalTauri' were unexpected)
       Error `tauri.conf.json` error: Additional properties are not allowed ('package', 'tauri' were unexpected)

Stack trace

Additional context

No response

[Legend-Master]

I think we don't really have the migrate command setup for v2-alpha -> v2 stable since there were so many breaking changes across those versions, but we should definitely print something out instead of doing nothing

At the mean time, does changing the version in Cargo.toml like this and then run cargo tauri migrate work? (this triggers it to migrate it like if it's upgrading from v1)

- tauri = { version = "2.0.0-alpha.8", features = ["api-all", "dialog", "updater"] }
+ tauri = { version = "1", features = ["api-all", "dialog", "updater"] }

[kornelski]

No, unfortunately it doesn't help.

I've copied a config from a blank project. WOW THERE WERE A LOT OF CHANGES. I don't think I can salvage the app. I have more errors than lines of code.

[Legend-Master]

That's unfortunate, there were lots of breaking changes between v1 and v2, and the migrate command only migrates the basics, like changing the feature flag to use the plugins, setting up permissions, and migrating the config files