On July 14, 2026, we released ghprmerge v0.5.0. This update marks a significant evolution in how you interact with the tool, introducing a more structured command-line interface and powerful new filters to help you manage cross-repository pull requests with greater precision.

What’s new

The headline change in v0.5.0 is the transition to a subcommand-based CLI. Instead of global flags, ghprmerge now organizes its operations into three distinct commands:

  • ghprmerge merge: Automatically evaluate and merge matching PRs.
  • ghprmerge rebase: Keep pull request branches up-to-date with their default branches.
  • ghprmerge report: Analyze and group open pull requests by source branch.

Beyond the structural changes, we’ve added new capabilities to refine your workflow:

  • Author Filtering: You can now use the --author <login> flag to target pull requests from a specific user or bot (such as app/dependabot), ensuring you only process the updates you intend to.
  • Minimum Group Size: For those using the report command, the new --min-group-size <n> flag allows you to filter out noise by excluding groups that contain fewer than a specified number of pull requests.
  • Granular Verbosity: The report command now offers three levels of output—brief, standard, and verbose—via the --verbosity flag, giving you exactly the amount of detail you need.
  • Improved CI Stability: We’ve ensured that the --no-progress flag is strictly respected across all operations, making the tool more reliable and cleaner when run in non-interactive environments like GitHub Actions.

Why it matters

As your organization grows and the number of automated dependency updates increases, the ability to filter and organize your PR management becomes critical. The new subcommand architecture not only makes the tool more intuitive to use but also sets the stage for future extensibility.

The addition of author filtering is a particular win for teams managing multiple automation bots, allowing for tailored merge strategies based on who (or what) created the PR. Combined with more flexible reporting, v0.5.0 transforms ghprmerge from a simple utility into a more robust orchestration tool for your GitHub organization.

Upgrade and Installation

Please Note: This release contains breaking changes to the CLI structure.

To upgrade, simply update your ghprmerge binary to v0.5.0. Because the tool has moved to a subcommand model, you will need to update any existing scripts or automation. Operational flags (such as --org, --repo, and --json) must now be placed after the subcommand.

Example updated command: ghprmerge merge --org my-organization --json

For detailed usage instructions, please refer to the updated documentation in the repository.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. Generated on July 14, 2026, based on the ghprmerge repository and v0.5.0 release. Author: release-storyteller