When to use this skill
ALWAYS use this skill when the user mentions:
- Upgrading from Tauri v1 to v2 / From v1 upgrade to v2
- Migrating from v2 beta to v2 stable / v2 beta migration to stable version
- Breaking changes in config or permissions / Config or permissions changes
Trigger phrases include:
- "migrate", "upgrade", "breaking changes", "v1 to v2"
- "upgrade", "migration", "config changes", "permissions changes"
How to use this skill
- Identify current version and target / Confirm current version and target version
- Review breaking changes across config, plugins, permissions / Inventory change points
- Update tauri.conf.json and plugin layouts / Update config and plugin locations
- Migrate capabilities/default.json and scopes / Migrate capabilities and Scope
- Validate IPC, CSP, and runtime behavior / Validate IPC, CSP, and runtime behavior
Outputs
- Migration checklist / Migration checklist
- Updated config mapping / Updated config mapping
- Post-upgrade validation plan / Post-upgrade validation plan
Scope
- Boundary: Version migration and validation only / Only migration and validation
- Key points: Config structure and capability system changes / Config and permissions system
- Out of scope: feature redesign / Does not include feature refactoring
References
- https://v2.tauri.app/start/migrate/
- https://v2.tauri.app/start/migrate/from-tauri-1/
- https://v2.tauri.app/start/migrate/from-tauri-2-beta/
Keywords
tauri upgrade, migrate, v2, breaking changes, config migration, upgrade, migration, config changes