RBTools 6.0 Release Notes¶$$$Release date: February 9; 2026$$$$$$Installation$$$Follow our installation guide to install RBTools.$$$$$$To learn more; see:$$$$$$Documentation$$$$$$RBTools on PyPI$$$$$$RBTools on GitHub$$$$$$Compatibility$$$RBTools supports Python 3.10 through 3.14.$$$$$$Support for Python 3.8 and 3.9 has been dropped. For continued support on those versions; please use RBTools 5.x.$$$$$$Added a dependency on appdirs. This replaces a previously bundled copy.$$$$$$Added a dependency on typelets 1.1.x.$$$$$$New Features$$$Added support for Jujutsu$$$$$$Jujutsu is a version control system which works seamlessly with Git servers while providing new and innovative concepts and commands. Because of its interoperability; it’s a powerful tool that can be integrated into individual developer workflows without requiring major organizational changes.$$$$$$RBTools 6.0 includes full support for working with Jujutsu clones; including posting; patching; and landing changes.$$$$$$Full documentation and type hinting for all resources.$$$$$$The Python API part of RBTools automatically generates client-side bindings by introspecting API payloads. While this allowed the bindings to be used for all APIs; including those in custom extensions; it made it difficult to work with because things like method names were not properly documented.$$$$$$The API now includes custom resource subclasses to match all resource endpoints in Review Board. These provide documentation and type hints for the entire API surface.$$$$$$Under the hood; the API still uses introspection; so you can still use it with your extension-provided API endpoints.$$$$$$Allow the --open-browser and --web-login options to be used for all commands.$$$$$$Web-based login (introduced in RBTools 5.0) was only supported for the rbt login command; which meant that the login prompts used for other commands when there was no current session would not allow it. This has been changed so if the server supports web-based login; it can be used at any point.$$$$$$rbt patch$$$Apply patches to binary files.$$$$$$As of Review Board 7.0 and RBTools 5.0; posted changes may include binary files in diffs. This is limited to reviewable file types such as images. “rbtcommand:rbt patch will now download these files and apply them as part of the patch.$$$$$$This is supported for Jujutsu; Git; Mercurial; Perforce; and Subversion.$$$$$$Bug Fixes$$$rbt land$$$Fixed an issue where an incorrect warning about private user profiles could be shown.$$$$$$rbt list-repo-types$$$Fixed a crash when dependencies for supported repository types were missing.$$$$$$rbt patch$$$Fixed some potential issues with commit messages and authors when squashing multiple commits.$$$$$$Fixed patching on Mercurial to use –config patch.eol=auto in order to more reliably apply patches in files with varying newline styles.$$$$$$Patch by André Klitzing

New Features$$$Added support for newer versions of Azure DevOps Server / Team Foundation Server.$$$$$$RBTools can now work with modern versions of tf from Visual Studio; making it easy to post your changes without maintaining multiple copies of TFVC.$$$$$$See the Azure DevOps / Team Foundation Server Configuration documentation for more information.$$$$$$Renamed our Cliosoft SOS support to Keysight SOS.$$$$$$Cliosoft SOS was purchased by Keysight; and is now Keysight SOS. RBTools now documents this as Keysight SOS and lists it in the list of supported repository types.$$$$$$See Using RBTools With Keysight SOS to learn more about using Keysight SOS.$$$$$$Bug Fixes$$$Installation$$$Fixed an issue running the rbt command after using the RBTools for Windows installer.$$$$$$Added back support for the rbt install command; used to install Azure DevOps Server / Team Foundation Server support.$$$$$$Azure DevOps Server / Team Foundation Server$$$Fixed parsing commit history containing Windows-style newlines.$$$$$$Git$$$Fixed using rbt post --exclude with filenames containing spaces. (Bug #5045)

New Features$$$Added support for newer versions of Azure DevOps Server / Team Foundation Server.$$$$$$RBTools can now work with modern versions of tf from Visual Studio; making it easy to post your changes without maintaining multiple copies of TFVC.$$$$$$See the Azure DevOps / Team Foundation Server Configuration documentation for more information.$$$$$$Renamed our Cliosoft SOS support to Keysight SOS.$$$$$$Cliosoft SOS was purchased by Keysight; and is now Keysight SOS. RBTools now documents this as Keysight SOS and lists it in the list of supported repository types.$$$$$$See Using RBTools With Keysight SOS to learn more about using Keysight SOS.$$$$$$Bug Fixes$$$Installation$$$Fixed an issue running the rbt command after using the RBTools for Windows installer.$$$$$$Added back support for the rbt install command; used to install Azure DevOps Server / Team Foundation Server support.$$$$$$Azure DevOps Server / Team Foundation Server$$$Fixed parsing commit history containing Windows-style newlines.$$$$$$Git$$$Fixed using rbt post --exclude with filenames containing spaces. (Bug #5045)

RBTools 5.2.1 Release Notes$$$Release date: April 23; 2025$$$$$$Bug Fixes$$$Fixed issues when running certain commands outside of a source tree with the TREES setting.$$$$$$Some commands; such as rbt patch --print or rbt api-get; can be run outside of a source tree; because they do not interact with the repository at all. RBTools 5.2 contained a regression when using these commands with the TREES setting; causing these commands to error out with a message about not being able to find the repository.

RBTools 5.2.1 Release Notes$$$Release date: April 23; 2025$$$$$$Bug Fixes$$$Fixed issues when running certain commands outside of a source tree with the TREES setting.$$$$$$Some commands; such as rbt patch --print or rbt api-get; can be run outside of a source tree; because they do not interact with the repository at all. RBTools 5.2 contained a regression when using these commands with the TREES setting; causing these commands to error out with a message about not being able to find the repository.