What problem does it solve? Upgrading a self-hosted n8n stack risks breaking workflows through removed nodes, renamed environment variables, and irreversible database migrations, and this Skill enforces a docs-verified audit, snapshot, and verification process before anything changes. ## Core Features & Use Cases - Docs-Verified Compatibility Audit: Cross-references official n8n release notes and BREAKING-CHANGES.md against your actual env vars, nodes, and database config, reporting only changes between your current and target versions. - Snapshot-Based Rollback: Captures compose files, credentials exports, database dumps, and the data volume (including the encryption key) before any upgrade, with a full restore procedure. - Active-Workflow Verification: Diffs active workflows and error executions via the n8n REST API before and after the upgrade, and fires a smoke-test workflow to prove the stack works. - Use Case: Your n8n is on 2.30.1 and the runners sidecar drifted to a different tag. Ask the agent to upgrade to the latest stable release; it produces a blocking-changes report for your approval, snapshots everything, bumps both tags together, and verifies every previously active workflow is still active. ## Quick Start Upgrade my n8n docker-compose stack in the current directory to the latest stable version and verify all my active workflows still work afterward.
