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:

• SCM Backup now requires .NET 8
  (contributed by lessismore-sparkvision)
• Dockerized version
  (contributed by lessismore-sparkvision)
• Bugfix: Ignore unknown properties in config file

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:

• new versions of dependencies
• the download now includes the license
• additional CI build for Linux

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

1.5.0

Changes:

• Backing up Bitbucket workspaces is now fully supported ⇒ Documentation
  Note: Bitbucket will make breaking API changes on October 14, which unfortunately means that backing up from Bitbucket with all SCM Backup versions < 1.5 won't work anymore!

• Process exit code is set to 0 on success and 1 on failure (thanks to nzbart for contributing this)

• The subject of the generated email now contains "Success" or "Failure"