Skip to main content

Release Notes

New features, improvements, and fixes. Here are the latest Tower updates!

Tower 4

With version 4, Tower allows you to undo many Git actions - simply by pressing CMD+Z.

What's New in Tower 4

  1. Undo

    Deleting branches and files, staging changes, rebasing & merging branches, or even publishing a branch on a remote: many Git actions can now be undone in Tower, simply by using the keyboard shortcut CMD+Z. Correcting mistakes has never been easier!

4.5

New

  • Repository Finder: It is now possible to specify directories which Tower should exclude when searching for repositories. You can find this in Tower’s Preferences on the “Advanced” tab.

  • Branches: We have added the option to delete the tracking branch when deleting a local branch.

Improved

  • Merging: The --no-commit option has been added to the merge dialog through the checkbox “Directly Commit Merged Changes”.

  • Sorting in Dialogs: Remotes are now being sorted by relevance in dialogs.

  • Azure DevOps Pull Requests: We have improved error mapping for errors that can occur when merging Azure DevOps Pull Requests.

  • Azure DevOps Server: Added support for authenticating with Personal Access Tokens.

Fixed

  • Check Out Pull Request: The Check Out Pull Request button is now validated again if the HEAD branch changes.

  • Check Out Pull Request: The Check Out Pull Request button is now disabled if the remote branch is not available.

  • Pull Requests: Creating pull requests now works as expected for forks on Bitbucket.

  • Pull Requests: In some cases, a newly created Pull Request was displayed in the list if it was created for another repository.

4.4

New

  • Azure DevOps Pull Requests: Pull Requests for Azure DevOps repositories are now supported in Tower.

Improved

  • Azure DevOps Service Accounts: The “Create Repository” button has been removed for Azure DevOps service accounts. The button is now available for organizations only.

Fixed

  • Azure DevOps Service Accounts: A crash which affected the creation of Azure DevOps service repositories has been fixed.

  • Switching Branches: Some users reported that switching branches and saving a stash with only untracked files in the Working Copy stopped working after our latest update.

4.3

New

  • Partial Stashing: You can now select individual files for stashing.

  • First Parent Filtering: It is now possible to filter out merged commits in the History view.

Improved

  • Commit Count Computing: For some users, this operation caused slowness in repositories with lots of commits. This has now been addressed.

  • GitHub's "Open in Desktop": GitHub's URL scheme for "Open in Desktop" changed; as a result users were no longer able to open a repository in Tower using this feature. This has been fixed.

Fixed

  • Crash when Saving a Stash: In some situations, Tower crashed when trying to save a stash.

  • Working Copy: After a commit, the File Detail View is now correctly updated.

  • Grouping Commits by Week: The "Group by Week" option in the History View wasn't working as expected.

  • Pull Request Changeset View: The changeset view is now being updated correctly when switching between Pull Requests.

  • Quick Actions: Remote branches are now correctly sorted by name.

4.2

Fixed

  • Pull Requests: A regression caused the pull request conversation view not being updated after changes have been made.

4.1

New

  • Pull Requests: Tower's search now also supports filtering Pull Requests by number.

Improved

  • Dialogs: In many dialogs, we have an "Options" area. Now, you can also click on the text label (not only the disclosure triangle) to reveal.

Fixed

  • Interactive Rebase: The auto-stash dialog now appears for all interactive rebase actions if required.

  • Pull Requests: If editing a pull request failed, the "Edit Pull Request" dialog is now shown again (instead of the dialog for editing the pull request body).

  • Pull Requests: The pull request commits and changeset views used to flicker when expanding a commit or changeset item. This has been fixed now.

  • Committing: A commit can now be created again if the HEAD is detached.

  • Remotes: In some rare situations, Tower crashed when a push was initiated.

  • Window Tabs: On older macOS versions, Tower crashed in some cases when opening a new tab.

4.0

New

  • Undo with CMD+Z: This new version makes it incredibly easy to undo many mistakes, simply by typing CMD+Z! Read more about this awesome new feature on our blog.

Improved

  • Reflog View: We've improved the refreshing of items in the Reflog view.

  • Excluding "Go" Module Caches: Tower's "Quick Open" dialog allows you to open any repository on your machine. However, users with "Go module caches" reported a slowdown in this dialog; that's why Tower now excludes these special repositories for the "Quick Open" search.

  • Bitbucket Server: Tower now supports personal access tokens for Bitbucket Server accounts.

  • Azure DevOps Server: With this update, accounts can now be created for multiple collections.

Fixed

  • History Badges: Clicking directly on a badge (representing a tag or branch) on a commit in one of Tower's history views sometimes failed to select the commit item.

  • Selecting Lines in Diffs: On macOS 10.15, some users reported a crash when trying to select individual lines for staging in a working copy diff.

  • Checkout Pull Request Menu Item: The menu item for our new "Checkout Pull Request" feature didn't work in all cases.

  • Saving Stashes: In some situations, Tower could crash when trying to save a stash.

  • Pull Request Comments: These are now sorted by creation date instead of updated date.

  • Renaming Remote Branches: If no local tracking branch existed, Tower didn't allow to rename a remote branch. This is fixed now.

  • History: When restoring user selections the application could become unresponsive in some cases

  • Avatar Image: In some cases, the font size calculated for drawing the user's initials was not a valid font size, leading to a crash

  • Diffs: Loading image data for diffs in the working copy could sometimes result in a crash

  • Window Titles: In some cases, Tower didn't display the correct titles from tabs.

  • A regression caused opening a new tab for a window without existing tabs opening in a new window instead. Tabs now open a new tab for the current window in all cases now.

  • Various crashes: We fixed a number of smaller / less common crashes in different situations.