Upgrade Guide

From v1.0.x → v2.0

• Database: Execute new migrations (log table indexes, notification table)
• Config: config/default.toml adds [notifications] section, defaults will auto-fallback
• Code: No breaking API changes; rebuild frontend dependencies
• Provider Modularization: New Provider registration flow (see Architecture Concepts/Service Providers)
• Config: jwt.secret renamed to security.jwt_secret; scheduler config hierarchy adjusted
• Migration: Task table and log table field changes (see migration notes for details)
• Frontend: Menu data structure adds meta field; upgrade adapter tool script provides schema migration

Recommended Process:

1. Backup database and .env
2. Switch branch and upgrade dependencies (cargo update; frontend: pnpm i)
3. Execute migrations
4. Gradual release, verify task scheduling and permission changes