ghprmerge V0.4.0: Streamlining Organization-Wide PR Management
Released on April 11, 2026, ghprmerge V0.4.0 introduces a significant evolution in how the tool is interacted with and operated. This release marks a transition to a more scalable CLI architecture and adds powerful new capabilities for users managing automated dependency updates across large GitHub organizations.
What’s new
A Modernized Command Interface
The most prominent change in V0.4.0 is the move from a flag-based system to a subcommand-based architecture. The previously used --merge, --rebase, and --report flags have been replaced by dedicated subcommands: merge, rebase, and report. This shift provides a clearer logical separation of tasks and prepares the tool for future growth.
Multi-Source Branch Support
Efficiency is key when managing hundreds of repositories. Users can now specify multiple --source-branch flags in a single command. Whether you are managing Dependabot, Renovate, or custom automation branches, you can now process them all in one execution rather than running the tool multiple times.
Visual Progress Overhaul
To improve the experience during long-running organization scans, we’ve completely rewritten the terminal progress bar. The new implementation uses high-resolution Unicode characters for smoother rendering and dynamic coloring—transitioning from cyan to yellow and finally green—giving you an immediate visual cue of the process’s status.
Why it matters
For maintainers of large-scale organizations, the overhead of managing automated PRs can be daunting. By introducing subcommands, ghprmerge becomes more intuitive to use and easier to script. The addition of multi-source branch support directly reduces the time and effort required to keep dependencies current across a diverse set of automation tools. Combined with the enhanced visual feedback, these changes make organization-wide maintenance more transparent and less tedious.
Upgrade and Migration
⚠️ Important: This release contains a breaking change.
Because of the shift to subcommands, existing CI/CD workflows and scripts must be updated to match the new syntax.
Migration Example:
- Old (v0.3.0):
ghprmerge --org myorg --merge --source-branch dependabot/ - New (V0.4.0):
ghprmerge --org myorg merge --source-branch dependabot/
To take advantage of the new multi-branch support, you can now run:
ghprmerge --org myorg merge --source-branch dependabot/ --source-branch renovate/
We encourage all users to update their automation scripts to V0.4.0 to benefit from these performance and usability improvements.
This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL on 2026-04-11, based on the ghprmerge V0.4.0 release. Author: release-storyteller