Releases: christianspecht/scm-backup
Releases · christianspecht/scm-backup
1.10.1
Once again, a bugfix for a breaking change in Bitbucket: App passwords (which SCM Backup used for authentication) will be replaced by API tokens:
It's no longer possible to create new app passwords, and all existing app passwords will stop working June 9, 2026. So everybody who is using SCM Backup to backup private Bitbucket repos has to switch to API tokens until then.
1.10.0
One new feature:
- Optional setting to upload backup folder to Amazon S3
(contributed by Andrew Lorien)
1.9.0
Changes:
- Optional setting to save backup in a new timestamped subfolder for each run
- Update for local docker debug, Git installed in base image
Thanks to lessismore-sparkvision for contributing both changes!
1.8.0
Changes:
1.7.1
One new feature:
- new config option: output a second log message when a repo's backup is finished
...and some "internal" improvements:
1.7.0
One new feature:
- New configuration setting
includeRepos: lets you specify a list of repos, only these repos will be backed up, all others will be ignored
⇒ Documentation
1.6.0
Changes:
- SCM Backup can detect (and optional delete) repos that were deleted from the hoster, but still are in the local backup dir
⇒ Documentation - Backing up repos whose name ends with
.is now possible
1.5.3
Changes:
- Logging improved under the hood.
Loggers can now:- backup their configuration files
- execute code when SCM Backup exits (which simplifies the code for the Emailing output feature)
1.5.2
Changes:
- Fix Bitbucket errors caused by Mercurial repos
(2 months after Bitbucket's Mercurial deprecation, their API still returns Mercurial repos but cloning/pulling them fails -> ignore them) - Show operating system on startup
1.5.1
One bugfix:
- Detecting if Mercurial is installed and determining the version number now works on non-English systems as well