Stash 2.5 release notes

12 June 2013

Go public with Stash 2.5

Today we're pleased to announce Stash 2.5, which fosters external participation and let's you enjoy even more streamlined code collaboration with public access to projects and repositories.

If you are upgrading from an earlier version of Stash, please read the Bitbucket Server upgrade guide.

The Stash 2.5 changelog is at the bottom of this page.

Public access to projects and repositories

Public access provides anonymous (unauthenticated) users with browse access to specific repositories or entire projects in Stash. Anonymous users can see the source code in a repository, and clone the repository.  Logged-in users get read access to a repository that has public access, so they can fork it and create pull requests. Public access doesn't allow your source code to be changed in any way.

You can configure public access to repositories and projects separately. You can also disable anonymous access by setting a global system property. Please refer to the Stash API changelog for information about how plugin design is affected by public access.

Read more about public access in Stash.

Edit a pull request's destination branch

You can now change the destination branch for an active pull request – if you set the wrong destination when creating the PR, you no longer have to delete it and create a new one.

Read more about pull requests in Stash.

Get more context in diffs

We've added a way for you to see more lines of code in the diffs for pull requests and commits. We think this will really help with using pull requests for code reviews. Just click on the grey bars to see more context, up to the whole file if you want. There may also be grey bars at the top or bottom of the diff, if more context is available there. 

Note that the expanded lines are displayed as greyed-out, to show that you can't comment on them.

Java OpenJDK is now supported

Java OpenJDK is widely used by Linux distributions. We've made your life easier by adding OpenJDK to the list of Java JDKs supported by Stash.

Just a reminder, Java 6 has been deprecated and will not be supported by Stash 3.0 (and later versions), which will be released later in 2013.

See Supported platforms for more information.

Small improvements

  • JIRA issues that only appear in forks are now linked to the JIRA server.
  • Stash now respects  .mailmap  files in Git repositories. See Git resources for details.
  • The SCM Cache plugin is now bundled - see Scaling Bitbucket Data Centre for Continuous Integration performance.
  • We've added a bit more control for CAPTCHA:
    • There is now a system property switch to turn off (and hide) the Maximum login attempts control (look under 'Authentication' in the admin area). 
    • Administrators are now able to clear a user's CAPTCHA status, from the user's profile:


Change log

This section will contain information about the Stash 2.5 minor releases as they become available. These releases will be free to all customers with active Stash software maintenance.

If you are upgrading from an earlier version of Stash, please read the Bitbucket Server upgrade guide.

The issues listed below are just the highlights of all those that have been resolved for the Stash 2.5 release.


11 November 2013 - Stash 2.5.4  (${entries.size()} issues)

T Key Summary

22 July 2013 - Stash 2.5.3  (${entries.size()} issues)

T Key Summary

03 July 2013 - Stash 2.5.2  (${entries.size()} issues)

T Key Summary

25 June 2013 - Stash 2.5.1  (${entries.size()} issues)

T Key Summary

11 June 2013 - Stash 2.5.0  (${entries.size()} issues)

T Key Summary

Last modified on May 14, 2015

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.