Releases: christianspecht/scm-backup
Releases · christianspecht/scm-backup
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
0on success and1on failure (thanks to nzbart for contributing this) -
The subject of the generated email now contains "Success" or "Failure"
1.4.1
There is only one change:
- Backing up repositories owned by a user from Bitbucket is working again (repositories owned by teams were not affected).
→ More details
1.4.0
1.3
- New: GitLab support
- Updated to .NET Core 3.1
- Updated all dependencies
1.2.2
1.2.1
Changes:
- Disabled some integration tests that work on my local machine, but never return on AppVeyor
- GitHub/Bitbucket: for backing up repos owned by users, enforce authentication with the same user
- Bitbucket API calls now use the user's UUID
Please note: Breaking changes in the Bitbucket API on April 29, 2019!
1.2.0
Mostly bugfixes and one breaking change (now requires .NET Core 2.1), hence the new minor version:
- Updated the project to .NET Core 2.1
- Bugfix: Mercurial authentication
- Bugfix: Emailing logs via SMTP server which doesn't require authentication
- Bugfix: Build script exit code
- Simplified executing the integration tests
1.1.1
1.1.0
Some bugfixes, and lots of new features:
- Now backs up private repos as well
- Bitbucket support
- The config file is backed up as well
- Console output can be sent via email
- Certain repos can be ignored