Skip to main content

Release Notes

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

Tower 13

Tower 13 is all about Graphite support!

This update introduces seamless Graphite integration for all the most popular actions, allowing you to manage your stacked branches and create Pull Requests without leaving Tower.

Watch this 5-minute video to discover everything you can do!

What's New in Tower 13

  1. Enabling the "Graphite" Workflow

    Enabling the "Graphite" Workflow

    To enable the "Graphite" workflow, click the "Workflow" toolbar button and select the Graphite workflow. You will then be able to quickly access some of Graphite's most popular commands and open the Graphite dashboard in your browser.

  2. Managing Stacked Branches

    Managing Stacked Branches

    You can create a new stacked branch by right-clicking on any existing branch. You'll also find all the other essential Graphite operations right here in the context menu: renaming, merging, squashing, deleting… you name it!

13.1

  • New

  • Added terminal integration support for WezTerm.

  • Fixed

  • Resolved a crash that could occur during pull request cleanup.

  • Resolved an issue where restack would fail if the repository path contained whitespace.

  • Working Copy: Expansion tooltips are now correctly displayed for truncated file paths.

13.0.3

Fixed

  • Rebase Onto: The "Rebase Onto" dialog did not open anymore. This has been fixed.

  • Pull Requests: The performance of removing stale pull requests from Towers cache has been improved.

  • History: Commit Signatures were verified even when the setting was turned off. This has been fixed.

13.0

New

  • Graphite: Tower now seamlessly integrates with the Graphite workflow!

Improved

  • History: Commit loading performance has been greatly improved when signature verification is turned on.

Fixed

  • History: The scroll position was reset to the top in some cases. This has been fixed.

  • History: The list could become empty if the verification of commit signatures failed. It's fixed.

  • History: Verifying signed commits could lead to 100% CPU usage due to GPG contacting key servers. Tower now disables automatic public key fetching to solve this problem.

  • Working Copy: Tower could crash if a user profile referenced an invalid signing key. This has been fixed.