Bug fixes

• SSH compression is disabled by default in ghe-ssh to improve performance during backup and restore operations. Previously, SSH compression was enabled by default, which could cause slowness. If you need to turn on compression for rsync large files like storage or git files, configure with GHE_RSYNC_COMPRESSION_ENABLED, or override this setting completely with GHE_EXTRA_SSH_OPTS set to -o IdentitiesOnly=yes.

• Administrators restoring backups using Backup Utils could experience missing Redis-related log entries or failed restore status in the UI.

Changes

• Incremental MySQL backup (-i or --incremental option) has been deprecated since 3.17. Restoring previous backups created with incremental MySQL backup option will remain supported.

Bug Fixes

• Site administrators restoring from backup saw chat integration settings for Slack and Microsoft Teams overwritten in staging environments, even when the -c flag was not specified with the ghe-restore command.

Bug Fixes

• Site administrators restoring from backup saw chat integration settings for Slack and Microsoft Teams overwritten in staging environments, even when the -c flag was not specified with the ghe-restore command.

Bug Fixes

• Site administrators restoring from backup saw chat integration settings for Slack and Microsoft Teams overwritten in staging environments, even when the -c flag was not specified with the ghe-restore command.

Bug Fixes

• The OIDC configuration for remote blob providers did not correctly update when restoring a backup into a new hostname.
• Site administrators restoring from backup saw chat integration settings for Slack and Microsoft Teams overwritten in staging environments, even when the -c flag was not specified with the ghe-restore command.

Bug Fixes

• Site administrators restoring from backup saw chat integration settings for Slack and Microsoft Teams overwritten in staging environments, even when the -c flag was not specified with the ghe-restore command.

Bug fixes

• Audit Log streaming decoding secrets are not backed up or restored.

Changes

• Incremental MySQL backup (-i or --incremental option) has been deprecated since 3.17. Restoring previous backups created with incremental MySQL backup option will remain supported.

• Restores will automatically detect incremental MySQL backups without requiring the -i flag.

Changes

• Restores will automatically detect incremental MySQL backups without requiring the -i flag.

Changes

• Restores will automatically detect incremental MySQL backups without requiring the -i flag.