We’re excited to announce the release of ghprmerge v0.2.1, a targeted enhancement that improves visibility during bulk merge and rebase operations. Released on March 14, 2026, this update addresses a key user experience concern: knowing what’s happening while your merge jobs run.

What’s New

The standout feature in v0.2.1 is real-time streaming of action results. When you run ghprmerge with the --merge or --rebase flags, you now see each operation’s result immediately as it completes—rather than waiting until all operations finish to see any feedback.

Before and After

Before (v0.2.0): Run a merge across 50 repositories, watch the progress bar march along silently, and only learn at the end which PRs merged successfully, which failed, and why.

After (v0.2.1): As each merge or rebase completes, you see instant feedback like:

  ✓ myorg/repo1 #42 Bump lodash to 4.17.21
    merged ─ successfully merged (all checks passing)
Scanning [██████████████████░░░░░░░░░░░░] 15/25 (60%)

The progress bar continues below, keeping you oriented while giving you immediate visibility into what’s working and what might need attention.

What’s Not Changed

  • Analysis-only mode remains unaffected—scan results still appear after the scan completes
  • The --verbose flag continues to work as before
  • All existing command-line flags function identically
  • JSON output format is unchanged

Why It Matters

Bulk dependency updates are a common workflow for modern DevOps teams. Tools like Dependabot automatically open pull requests across your entire organization, but manually clicking through each repository to merge them is impractical at scale. ghprmerge solves this by automating the evaluation and merging process—but until now, users had no visibility into what was happening during execution.

This release closes that feedback gap. Whether you’re merging 10 repositories or 100, you can now watch progress in real-time, spot issues as they occur, and gain confidence that operations are proceeding correctly.

Safety First

Remember: ghprmerge is designed to be safe by default. Without the --merge or --rebase flags, it runs in analysis-only mode—no mutations occur unless you explicitly request them. The new streaming behavior only affects these explicit action modes, giving you more transparency when you choose to take action.

Getting Started

Upgrading to v0.2.1 is straightforward—there are no breaking changes or migration steps required. Simply download the latest binary for your platform:

Linux:

curl -L https://github.com/UnitVectorY-Labs/ghprmerge/releases/latest/download/ghprmerge_linux_amd64 -o ghprmerge
chmod +x ghprmerge
sudo mv ghprmerge /usr/local/bin/

macOS (Intel):

curl -L https://github.com/UnitVectorY-Labs/ghprmerge/releases/latest/download/ghprmerge_darwin_amd64 -o ghprmerge
chmod +x ghprmerge
sudo mv ghprmerge /usr/local/bin/

macOS (Apple Silicon):

curl -L https://github.com/UnitVectorY-Labs/ghprmerge/releases/latest/download/ghprmerge_darwin_arm64 -o ghprmerge
chmod +x ghprmerge
sudo mv ghprmerge /usr/local/bin/

Windows:
Download ghprmerge_windows_amd64.exe from the releases page and add it to your PATH.

From Source:

go install github.com/UnitVectorY-Labs/ghprmerge@v0.2.1

For complete command-line documentation and usage examples, visit the full documentation.

This post was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. Research based on the v0.2.1 release from the UnitVectorY-Labs/ghprmerge repository, published March 14, 2026. Author: release-storyteller.