-
Notifications
You must be signed in to change notification settings - Fork 624
Release 2.20.0 #565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.20.0 #565
Conversation
…rt-mysql-mysqldump
Use sentinel file to identify type of mysql backup
Make sure the absence of audit_entries table is not fatal
…g '-gitbackups' variant
… but is missing required script to do so
update wording Co-Authored-By: Caine Jette <[email protected]>
Add support for backing up repositories via gitbackups
Allow specifying base branch for release script
Add `ghe-` prefix to repository backup script
Bump version: 2.20.0
Revert "Bump version: 2.20.0"
Bump version: 2.20.0
Revert "Bump version: 2.20.0"
/cc @github/ghes-infrastructure for merge conflict resolution. |
# backup-utils 2.13 onwards limits support to the current and previous two releases | ||
# of GitHub Enterprise Server. | ||
supported_minimum_version="2.17.0" | ||
supported_minimum_version="2.18.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be 2.20?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. We support N-2 releases like we do for GHES upgrades as we need to support migrations.
@github/ghes-infrastructure can you approve this PR for merging if it is correct? Possibly related to #543 and https://github.com/github/backup-utils/issues/568. |
|
use backup-utils master branch instead of stable as its not merged into stable on backup-utils related to github/backup-utils#565
…he-unsupported-version-test Backport 545 for 3.8: Fix GHE unsupported version check
@Faisal78123 brought up that 2.20.0 is not present in stable. This PR brings in the
release-2.20.0
branch from #564 to stable.