Today, we are pleased to announce the availability of the new version of the Scala-based self-hosting Git server GitBucket 4.47.0!

Note that this release includes a large database migration affecting core tables such as REPOSITORY and ACCOUNT. We strongly recommend backing up your database before upgrading to GitBucket 4.47.0.

Here are the major changes and new features in this version.

More securiry for repository creation by cloning

GitBucket now provides additional controls for creating repositories by cloning an external repository. Administrators can disable this operation entirely when it is not needed. Also, private addresses blocking are applied to cloning, helping to prevent GitBucket from accessing internal network services through a clone URL.

Configurable password reset link expiration

Administrators can now configure how long password reset links remain valid. This setting is available from the system settings page and allows each installation to choose an expiration period appropriate for its security policy.

Improved GitHub API compatibility and fork management

GitBucket now assigns repositories a unique numeric ID to improve compatibility with the GitHub API. Fork management has also been improved, including handling relationships between parent repositories and forks when repositories are renamed, transferred, or deleted.

Additionally, auther and comitter icnluded in API repsonses become null when the user is not registered in GitBucket, following the GitHub API’s behavior.

Markdown code formatting improvement

The markdown formatting actions in the text editor have been improved. Previously, there are separate buttons for block code formatting and inline code formatting, but they are now merged.

This release also includes other improvements and bug fixes. See all closed issues in 4.47.0 for details.

Enjoy GitBucket!