Storage schema upgrade failure involving LevelDB prevents Atom from starting

Storage schema upgrade failure involving LevelDB prevents Atom from starting

When Atom encounters a storage schema version mismatch at startup, it runs a migration script; if the script throws an exception, the process aborts and the storage database is left in a partially migrated state, blocking further launches until the user manually deletes or repairs the storage directory.

This behavior leaves no automatic rollback, risks loss of window state and workspace layouts, and raises the question of whether a versioned backup‑and‑restore strategy should be introduced for storage migrations.

• Should Atom implement a versioned backup‑and‑restore mechanism for storage migrations?
• What degree of automation is acceptable for rolling back a failed migration?
• How can Atom verify migration success before committing the schema change?