Here are major changes and new features in this version.

Support for reverting pull requests

You can now revert a merged pull request directly from the pull request page. This makes it much easier to undo changes introduced by a pull request without manually creating a revert commit.

Markdown toolbar

A markdown toolbar has been added to the issue / pull request comment editor as well as other markdown editing areas. The toolbar provides quick-access buttons for common formatting operations, making it easier to write markdown content in GitBucket.

Text completion in Ace editor

Text completion using a suggestion provider has been added to editors. This helps you write content more efficiently by offering suggestions as you type.

Ace Editor for Wiki editing

The Ace Editor is now used for Wiki page editing, bringing syntax highlighting, customizable keybindings (e.g. Vim, Emacs), and a better overall editing experience to the Wiki.

SHA-256 webhook signatures

WebHook requests now include the X-Hub-Signature-256 header in addition to the existing SHA-1 signature. This allows webhook consumers to verify payloads using the more secure SHA-256 algorithm.

UTF-8 BOM preservation in web editor

When editing a file that contains a UTF-8 BOM (Byte Order Mark) through the browser, the BOM is now correctly preserved on save. Previously the BOM was silently stripped, which caused problems for files that require it.

This release also includes some other improvements. See all closed issues in 4.46.0 for details.

Enjoy GitBucket!

Here are major changes and new features in this version.

New option to display full username on UI

GitBucket only displayed username on its UI. However, there have been multiple reports that it’s not conveient when LDAP integration is used and username managed by LDAP is not human readable.

In this version, we added new option to show fullname of users along with username. This option can be enabled at the system settings.

Support render plugin in issues, pull requests, etc

GitBucket provides a mechanism to add file renderers to plugins. Plugins can extend even the markdown render using this mechanism but it wasn’t applied to issues, pull requests, wiki, commit comments, etc. The alternative markdown render added by a plugin is now applied to those contents.

This release also includes many bugfixes and improvements. See all closed issues in 4.45.0 for details.

Migration of GitBucket Community Plugins Web Site

We are also announcing the deprecation of GitBucket Community Plugins web site.

To reduce maintenance costs and improve sustainability of the project, we stopped maintaining the dedicated web site and moved the list of community plugins to a wiki page in the GitBucket’s repository: https://github.com/gitbucket/gitbucket/wiki/Community-Plugins

Anyone can edit this web page, so please add plugins yourself when you developped new ones. We are really looking forward to seeing new plugins there!

Enjoy GitBucket!

Here are major changes and new features in this version.

Enhanced branch protection

In previous versions, GitBucket’s branch protection only supported the following restrictions, and the standard functionality couldn’t prevent direct pushes to branches.

• Prevent force pushes to and deleting specified branches
• Prevent PRs that have not passed the status check from being merged

This version enhances branch protection and supports the following settings:

• Prevent pushes from non-allowed users
• Whether to apply restrictions to administrator users as well

Improve logging for initialization errors

In previous versions, even if an error occurred during startup, the log would not be displayed, making it appear as if it had frozen. However, we have improved the logging so that even initialization errors are properly logged, which would be helpful when you encounter troubles in setting up GitBucket.

This release also includes many bugfixes and improvements. See all closed issues in 4.44.0 for details.

Enjoy GitBucket!

This release is mainly for upgrading H2 from 1.x series to 2.x series. Note that you have to migrate your H2 database manually because H2 1.x and 2.x don’t have compatibility in the date file format if you use it.

Below is an example of the migration steps. Please do not forget taking a backup before the migration.

# Export database using the current version of H2
$ curl -O https://repo1.maven.org/maven2/com/h2database/h2/1.4.199/h2-1.4.199.jar
$ java -cp h2-1.4.199.jar org.h2.tools.Script -url "jdbc:h2:~/.gitbucket/data" -user sa -password sa -script dump.sql

# Recreate database using the new version of H2
$ curl -O https://repo1.maven.org/maven2/com/h2database/h2/2.3.232/h2-2.3.232.jar
$ java -cp h2-2.3.232.jar org.h2.tools.RunScript -url "jdbc:h2:~/.gitbucket/data" -user sa -password sa -script dump.sql

In addition, if your ~/.gitbucket/database.conf has the following configuration, you need to remove ;MVCC=true from url.

db {
  url = "jdbc:h2:${DatabaseHome};MVCC=true" // => "jdbc:h2:${DatabaseHome}"
  ...
}

This release also includes some bugfixes, improvements, and internal library updates. See all closed issues in 4.43.0 to know details.

Enjoy GitBucket!

Here are major changes in this version.

Increase max branch name length 100 -> 255

While Git accepts long branch names, GitBucket has its own max branch name length limit when creating pull request and configurating branch protection.

Until the previous version, the max length was 100 chars but it’s now 255 chars. In addition, error message is properly shown in the pull request creation form when pull request can’t be created.

Fix some GitHub incompatible Web APIs

Fixed response of list-repository-tags API and payload of webhook which were not compatible with GitHub.

Apply user-defined CSS after all plugins

Some plugins insert CSS dynamically using JavaScript and it’s can override user-defined CSS.

In this version, user-defined CSS is applied after plugin’s JavaScript to prevent overriding by plugins.

Improve performance of listing commit logs

Improve GitBucket’s internal implementation which would gain the performance of listing commit logs in many places in GitBucket when the target repository has many commits.

Even when pushing a branch, GitBucket intenally lists existing commits to identify new commits. The performance of this kind of processes would be also improved.

Java 17 is now required

Java 11 support is dropped in this version to support newer version of Jetty. Java 17 is now required to run GitBucket.

This release also includes some bugfixes, improvements, and internal library updates. See all closed issues in 4.42.0 to know details.

Enjoy GitBucket!

Here are major changes and new features in this version.

Simplify pull request UI

Merge action in the pull request UI is simplified a little.

Keyword search for issues and pull requests

Keyword search is supported in the search box of issues and pull requests view. If you search by keyword, it’s redirected to the keyword serach results.

Max diff display settings

Large diff could make the browser very heavy as it’s rendered by JavaScript. You can avoid it by configuraing max files and lines limit in showing diff at the system settings.

Adjust the default branch when cloning external repository

When creating a repository on GitBucket by cloning an external repository, the default branch has been set based on the default configuration of GitBucket. But it has caused an error at the repository viewer when the branch doesn’t exist.

Since this version, either of main or master is automatically chosen when the default branch doesn’t exist.

This release also includes some bugfixes, performance improvements, and internal library updates. See all closed issues in 4.41.0 to know details.

Enjoy GitBucket!

Here are major changes and new features in this version.

Configurable default branch name

The default branch can be now configurable though the default branch name is still master. Chaning the default branch name to main will be considered in the future version.

Support custom fields of issues and pull requests in search condition

You can use custom fields in the search condition of issues and pull requests.

Search expressions like field_name=value, field_name<value, etc. can be used in the search box for issues and pull requests.

Create pull request from default branch of forked repositories

Creating a pull request from the default branch of forked repositories hasn’t been allowed historically, but it’s possible in this version.

News feed shows activities of all visible repositories

In the new feed, only activities of owned repositories have been shown until this version. Now activities of all visible repositories are shown in the news feed which means even collaboators can see activities on repositories.

Drop Java 8 support

Java 8 support is no longer supported. You need to upgrade your Java installation to Java 11 or later if your GitBucket is running on Java 8.

Improve git push performance

The prformance of git push is improved in this version though it may not be enough for very large repositories. We will continue looking for another opportinity of imporving the performance more.

This release also includes many bugfixes mainly regarding Web APIs. See all closed issues in 4.40.0 to know details.

Enjoy GitBucket!

Here are major new features in this version.

Enum support in custom fields

Custom field for Issues and Pull requests have been supported since GitBucket 4.38.0 and enum type is now supported.

You can define enum field with comma-separated values so users can select one of these values from the pulldown list when create or edit issues or pull requests.

Hide large diff by default

GitBucket has an issue that it takes very long time to render very large diff. In this version, such large diffs that have more than 1000 lines are hidden by default. You can see these diffs by clicking “Show diff” link.

New options to run GitBucket using multiple machines

The following new experimental options are added in this version. These options can be used if you want to run GitBucket using multiple clusters for high availability or load balancing.

• --disable_news_feed
• --disable_cache

Note that these options are experimental and still GitBucket doesn’t support running using multiple machines officially. You can try it at your own risk.

This release also includes many bugfixes mainly regarding Web APIs. See all closed issues in 4.39.0 to know details.

Enjoy GitBucket!

Custom fields for Issues and Pull requests

Issues and Pull requests have a big improvement in this version that is custom fields!

You can add additional fields to Issues and Pull requests at the reporitory settings.

Multiple assignees for Issues and Pull requests

Another improvenemnt in Issues and Pull requests is that multiple assignees is now supported.

Of course, SMTP must be configured to use this feature as email will be sent when users request a password reset.

Reset password by users

Users can reset password by themselves if they forget it or when necessary for other reasons.

This feature is disabled by default. GitBucket admin can enable the future at the system settings.

Horizontal scroll for too wide tables in Markdown

Markdown rendering has been improved to show a horizontal scroll bar for too wide tables.

Jetty idle timeout configuration in standalone mode

New command line option --jetty_idle_timeout has been added to configure Jetty idle timeout configuration in standalone mode. The defauly value is 300000 = 5 min.

This release also includes various improvements and bug fixes. See all closed issues in 4.38.0 to know details.

Enjoy GitBucket!

Custom SSH URL

In case you have a proxy server for SSH access in front of GitBucket, you can now configure SSH URL at the system settings page.

EDDSA key support for signed commit verification

By upgrading apaceh-sshd and bouncycastle-java, GitBucket now supports EDDSA keys for signed commit verification.

Relax some text length limitations

Relaxed the following text length limitations:

• Password (20 -> 40)
• WebHook URL (200 -> 400)

Web API enhancements

The followig enhancements regarding Web APIs have been implemented in this version. Especially, Git Reference APIs enhancements would improve Jenkins integration:

• Enhance Git Reference APIs
• Add milestone data to issue list API
• Support “all” in issue list API

This release also includes various improvements and bug fixes. See all closed issues in 4.37.0 to know details.

Enjoy GitBucket!