v2.0.0

Drive Backup 2.0 is here, hooray! 🎉

This is a huge step forward for the project. The underlying backup mechanisms are mostly the same but this brings a lot more polish to the interface and project as a whole.

Notable Changes

• App includes its own client credential. It is no longer necessary to supply your own client credential to use. You still have the option to supply your own if desired (--client-credentials option).
• Each time a backup is run a configuration file is created/updated (drive-backup.bkp). By default this file will be placed in the backup's destination directory. If you want to run a previous backup again, you can supply the --backup-config option and all the settings from the previous backup will be used. This is very convenient and less error prone compared to manually supplying multiple options in the command line each time a backup is rerun.
• You can now set where the log file will be stored with --log-path.
• You can turn the completion notifications off for mac or Windows via --no-notifications.
• Can be installed via pipx or downloaded as a standalone binary that will be included with this release (and every release going forward).

Check the README for more info on how to use Drive Backup and any of the new features.

What's Changed

• Bump httplib2 from 0.12.0 to 0.18.0 by @dependabot in #1
• Bump httplib2 from 0.18.0 to 0.19.0 by @dependabot in #2
• Drive Backup 2.0 by @dunkmann00 in #6
• Fix glob pattern error for release workflow asset upload by @dunkmann00 in #7
• Fix cache key creation for macos release by @dunkmann00 in #8

New Contributors

• @dependabot made their first contribution in #1
• @dunkmann00 made their first contribution in #6

Full Changelog: https://github.com/dunkmann00/Drive-Backup/commits/v2.0.0