Bitbucket Server 5.13 release notes
7 August 2018
Interested in trying a shiny new version? Don't forget to renew your active software maintenance! Renew now.
If you are upgrading from an earlier version, refer to the Bitbucket Server upgrade guide.
Be sure to also check the End of support announcements for Bitbucket Server and the changes listed in the API changelog.
The Bitbucket 5.13 changelog is at the bottom of this page.
Support for Git protocol version 2
Git 2.18.0 introduces a new wire protocol, called git protocol version 2. The original (now dubbed v1) is a multi-step, back-and-forth between the client and server, to determine the minimal set of objects to be retrieved from the server. The original protocol had a number of issues:
- It always advertised all refs (list of current branches and tags + the commit IDs to which they currently referred). For repositories with many thousands of branches/tags, this involved sending megabytes of data across the wire, even if the client is only interested in a single or a few branches.
- The protocol was stateful: subsequent steps in the protocol depended on the information that was exchanged in prior steps. This statefulness made it more complex for clients to implement the git wire protocol.
- The protocol was designed around negotiating a 'pack' of objects to send from the server to the client, or vice versa. It was very specific and made it hard to extend, to support newer use cases such as GVFS.
Bitbucket Server now supports protocol 1 and 2, and will use protocol 2 if the Git client requests it. Please note that in Git 2.18.0, protocol 1 is still the default for Git clients. This can be changed through a git configuration setting (on the client).
In order to use protocol version 2, you will need to update Git to 2.18.0 on both server and clients. Find out how to upgrade Git in Bitbucket Server, or find the full announcement on the Google open source blog.
Adding labels to a repository, available now in Bitbucket Server 5.13
When repositories are split across multiple teams, projects, or even organizations, it can be very difficult to locate the repositories you're interested in. Using labels, it's now much easier to categorize and find related repositories.
You can add a maximum of five unique labels per repository.
If you have repository admin permissions for the repository, head to the label-component at the end of the page (under the README), and click to start typing your new label.
You can then click the label to see everything classified with that label.
Changelog
This section will contain information about the Bitbucket Server 5.13 minor releases as they become available. These releases will be free to all customers with active Bitbucket Server software maintenance.
If you are upgrading from an earlier version of Bitbucket Server, check the Bitbucket Server upgrade guide.
The issues listed below are the highlights of all those that have been resolved for the Bitbucket Server 5.13.x releases, and are ordered by votes received.