Backup creation limit for Quasar CLI upgrade safety in v2.x

Quasar CLI’s quasar upgrade command updates @quasar/app and related packages to the latest stable release using the project’s package manager. The command does not create any backup of package.json, lockfiles or source code before modifying dependencies. As a result, recovering from a failed upgrade depends on manually reinstalling the previous version recorded in the lockfile or reverting via version control, which assumes those files are committed and accurate.

Given that Quasar v2.x (Vue 3 based) lacks an automatic rollback feature, the decision about whether the CLI should generate a backup during upgrade remains unresolved. Teams must weigh the safety benefits of an implicit backup against potential overhead and storage concerns.

Should the CLI automatically back up critical files before an upgrade? What limits, if any, should be placed on the backup retention policy? How can users verify that a backup is sufficient for a reliable rollback without relying on external VCS?