> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trunk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Recent updates to Trunk Merge Queue.

## 2026

### November 2026

**November 10, 2026**

**[Browser Extension 1.12.0: GitHub's new pull request Overview page](https://docs.trunk.io/changelog/2026-11-10-browser-extension-1-12-0.md)**

The Trunk browser extension 1.12.0 supports GitHub's redesigned pull request Overview page.

### October 2026

**October 6, 2026**

**[Merge Queue: Skip Redundant Bisection Tests](https://docs.trunk.io/changelog/2026-10-06-merge-queue-skip-redundant-bisection-tests.md)**

Bisection now skips combinations of PRs that already failed and re-splits them right away, saving CI runs and time.

### August 2026

**August 26, 2026**

**[Browser Extension 1.0: Out of beta](https://docs.trunk.io/changelog/2026-08-26-browser-extension-1-0.md)**

The Trunk browser extension graduates from beta with more reliable queue controls, clearer failure details, and groundwork for expanding Merge Queue beyond GitHub.

### July 2026

**July 31, 2026**

**[Merge Queue: Stacked pull request support](https://docs.trunk.io/changelog/2026-07-31-merge-queue-stacked-pull-requests.md)**

Trunk Merge Queue now natively supports GitHub stacked pull requests — enqueue any PR in a stack and Trunk tests and merges the whole stack together.

### June 2026

**June 29, 2026**

**[Browser Extension: Performance and bug fixes](https://docs.trunk.io/changelog/2026-06-29-browser-extension-0-13-0.md)**

The Trunk browser extension 0.13.0 ships performance improvements and bug fixes.

**June 18, 2026**

**[Merge Queue: Queue and Graph Tabs Now Refresh on Return](https://docs.trunk.io/changelog/2026-06-18-merge-queue-stale-tab-refresh-fix.md)**

Switching back to the Queue or Graph tab now shows up-to-date data immediately instead of waiting for the next poll interval.

**June 17, 2026**

**[Merge Queue: Inline Queue Metrics Drilldown and Browser Extension Updates](https://docs.trunk.io/changelog/2026-06-17-merge-queue-metrics-and-extension-updates.md)**

Queue Metrics now drills down inline like Testing Metrics, and the browser extension hides the GitHub 'unable to merge as stack' row.

**June 15, 2026**

**[Merge Queue: Per-Queue Browser Extension Admin Control](https://docs.trunk.io/changelog/2026-06-15-merge-queue-browser-extension-admin-control.md)**

Org admins can now enable or disable the Trunk browser extension for each merge queue branch directly from the queue's settings page.

**June 12, 2026**

**[Merge Queue: Export Health Metrics as CSV](https://docs.trunk.io/changelog/2026-06-12-merge-queue-health-metrics-csv-export.md)**

Download any health chart's data as a CSV file directly from the Merge Queue Health dashboard.

**June 12, 2026**

**[Merge Queue: Settings Page Now Has Organized Sections](https://docs.trunk.io/changelog/2026-06-12-merge-queue-settings-section-hierarchy.md)**

Merge Queue settings are reorganized into a sidebar with named sections, each with its own URL for direct linking.

**June 11, 2026**

**[Merge Queue: Priority Badge and Impacted Targets Tooltip on PR Details Page](https://docs.trunk.io/changelog/2026-06-11-merge-queue-priority-badge-pr-details.md)**

The PR details page in the Merge Queue dashboard now shows the priority badge and a tooltip when no impacted targets have been uploaded.

**June 10, 2026**

**[Merge Queue: Enable or Disable PR State Labels](https://docs.trunk.io/changelog/2026-06-10-merge-queue-state-labels-setting.md)**

A new toggle in Merge Queue Settings lets you enable or disable GitHub labels that Trunk applies to pull requests to reflect their current queue state.

**June 8, 2026**

**[Merge Queue: Browser Extension Now Supports Firefox](https://docs.trunk.io/changelog/2026-06-08-merge-queue-firefox-extension.md)**

The Trunk browser extension is now on Firefox Add-ons, with full feature parity with the Chrome build.

**June 4, 2026**

**[Merge Queue: Resubmit From the Chrome Extension and Hide Noisy GitHub Rows](https://docs.trunk.io/changelog/2026-06-04-merge-queue-chrome-extension-0-8-0.md)**

The Trunk for GitHub Chrome Extension now shows why a PR left the queue with one-click resubmit, and lets you hide the GitHub merge-box rows it replaces.

### May 2026

**May 19, 2026**

**[Merge Queue: Chrome Extension Quality-of-Life Updates](https://docs.trunk.io/changelog/2026-05-19-merge-queue-chrome-extension-updates.md)**

Automatic bot comment hiding, a skip-batching toggle, and Celebration Mode come to the Trunk for GitHub Chrome Extension.

**May 19, 2026**

**[Merge Queue: Enqueue Pull Requests by Label](https://docs.trunk.io/changelog/2026-05-19-merge-queue-enqueue-by-label.md)**

Apply a configured GitHub label to a PR to send it straight to the merge queue.

**May 13, 2026**

**[Merge Queue: Testing Duration Chart](https://docs.trunk.io/changelog/2026-05-13-merge-queue-testing-duration-chart.md)**

Track how long PRs spend in the testing phase of the merge queue, then drill into individual test runs.

### April 2026

**April 30, 2026**

**[Merge Queue: Chrome Extension](https://docs.trunk.io/changelog/2026-04-30-merge-queue-chrome-extension.md)**

The Trunk Chrome Extension brings merge queue controls directly into your GitHub pull request page.

**April 28, 2026**

**[Merge Queue: Failure Statuses and Merge Item IDs on Test Runs](https://docs.trunk.io/changelog/2026-04-28-merge-queue-failure-statuses-merge-item-ids.md)**

The testing details API now reports which PRs a merge item is waiting on when tests pass, and the specific failure status when tests fail.

**April 21, 2026**

**[Merge Queue: Drill Down Into Merge Metrics](https://docs.trunk.io/changelog/2026-04-21-merge-queue-drill-down-into-merge-metrics.md)**

Merge Queue Health metrics can now be drilled down to the individual pull requests behind any data point.

**April 13, 2026**

**[Merge Queue: Terraform Provider](https://docs.trunk.io/changelog/2026-04-13-merge-queue-terraform-provider.md)**

Merge Queue can now be managed fully through Terraform. Previously, creating, updating, and managing a Trunk Merge Queue was a manual process handled through our UI.

### March 2026

**March 26, 2026**

**[Merge Queue: Testing Details API Now Includes Impacted Target Information](https://docs.trunk.io/changelog/2026-03-26-merge-queue-testing-details-api-now-includes-impacted-target-information.md)**

The Get Testing Details API now returns impacted target information, giving CI systems everything they need to launch the right tests.

**March 25, 2026**

**[Merge Queue: Multiple Queues Per Repo with Grouped Selector](https://docs.trunk.io/changelog/2026-03-25-merge-queue-multiple-queues-per-repo-with-grouped-selector.md)**

Previously, a repo could only have one queue. Now you can create additional queues from the merge queue creation page. The repo selector shows repos that already have queues and how many exist.

**March 25, 2026**

**[Merge Queue: Slack App Home Tab](https://docs.trunk.io/changelog/2026-03-25-merge-queue-slack-app-home-tab.md)**

The Trunk Slack App Home tab is now a full control plane for your merge queue activity across all your organizations.

**March 19, 2026**

**[Merge Queue: List Pull Requests Public API Endpoint](https://docs.trunk.io/changelog/2026-03-19-merge-queue-list-pull-requests-public-api-endpoint.md)**

A new POST /v1/listPullRequests endpoint lets you query all PRs in your merge queue programmatically. Filter by state (not ready, pending, testing, merged, failed, cancelled), time range, and…

**March 19, 2026**

**[Merge Queue: Route Slack Notifications to Multiple Channels](https://docs.trunk.io/changelog/2026-03-19-merge-queue-route-slack-notifications-to-multiple-channels.md)**

Merge queue Slack notifications can now be routed to multiple channels. Previously, notifications went to a single configured channel.

**March 13, 2026**

**[Merge Queue: Isolate PRs from Batching with noBatch](https://docs.trunk.io/changelog/2026-03-13-merge-queue-isolate-prs-from-batching-with-nobatch.md)**

PRs can now opt out of batching to test in isolation. When a high-risk PR is in the queue, batching it with other PRs means a failure forces the entire batch to restart.

**March 13, 2026**

**[Merge Queue: Prometheus-Compatible Metrics Endpoint](https://docs.trunk.io/changelog/2026-03-13-merge-queue-prometheus-compatible-metrics-endpoint.md)**

Merge Queue now exposes a Prometheus-compatible metrics endpoint for integration with your existing monitoring stack.

**March 9, 2026**

**[Merge Queue: Impacted Targets Visible on the Merge Graph](https://docs.trunk.io/changelog/2026-03-09-merge-queue-impacted-targets-visible-on-the-merge-graph.md)**

The merge graph now shows impacted targets directly on nodes and edges, so you can see exactly why PRs are connected and which targets they share.

**March 5, 2026**

**[Merge Queue: Custom Merge Commit Titles](https://docs.trunk.io/changelog/2026-03-05-merge-queue-custom-merge-commit-titles.md)**

You can now customize the merge commit title for any PR in the queue. Add merge-commit-title: Your custom title here on its own line anywhere in your PR body, and the merge queue will use that as the…

### February 2026

**February 6, 2026**

**[Merge Queue: Public API for Queue Management](https://docs.trunk.io/changelog/2026-02-06-merge-queue-public-api-for-queue-management.md)**

You can now fully manage your merge queues through the Trunk API without touching the web UI.

### January 2026

**January 30, 2026**

**[Merge Queue: Personal Slack Notifications](https://docs.trunk.io/changelog/2026-01-30-merge-queue-personal-slack-notifications.md)**

Get direct messages in Slack about your PRs in the merge queue, keeping you informed without adding noise to team channels and allowing you to address failures immediately.

**January 23, 2026**

**[Merge Queue: Support Additional Merge Methods](https://docs.trunk.io/changelog/2026-01-23-merge-queue-support-additional-merge-methods.md)**

You can now select your preferred merge method for PRs going through the merge queue. Previously, Trunk Merge only supported squash merging, which combines all commits into a single commit.

**January 14, 2026**

**[Merge Queue: Filter Metrics by Impacted Targets](https://docs.trunk.io/changelog/2026-01-14-merge-queue-filter-metrics-by-impacted-targets.md)**

Now you can filter merge queue health metrics by impacted targets to see exactly how well this parallel workflow is performing for each part of your codebase.

**January 9, 2026**

**[Merge Queue: Direct Merge to Main](https://docs.trunk.io/changelog/2026-01-09-merge-queue-direct-merge-to-main.md)**

Skip redundant testing and merge immediately when your PR is already up-to-date and the queue is empty

**January 7, 2026**

**[Merge Queue: Independent Concurrency for Batch Bisection](https://docs.trunk.io/changelog/2026-01-07-merge-queue-independent-concurrency-for-batch-bisection.md)**

When a batch of PRs fails and needs to be split apart to identify the culprit, you want those bisection tests to run as fast as possible so developers get quick feedback about what broke.

**January 2, 2026**

**[Merge Queue: Test Caching for Batch Failure Isolation](https://docs.trunk.io/changelog/2026-01-02-merge-queue-test-caching-for-batch-failure-isolation.md)**

When you use batching mode, the merge queue tests multiple PRs together for efficiency. If a batch fails, the queue needs to figure out which specific PR caused the problem by splitting the batch…

## 2025

### May 2025

**May 28, 2025**

**[Merge Queue: Failure tab only displays current failures](https://docs.trunk.io/changelog/2025-05-28-merge-queue-failure-tab-only-displays-current-failures.md)**

We’ve updated the Merge Queue Failure tab so that only PRs that failed and have not been resubmitted to the queue are displayed.

**May 8, 2025**

**[Merge Queue: Webhooks on batched PR merges](https://docs.trunk.io/changelog/2025-05-08-merge-queue-webhooks-on-batched-pr-merges.md)**

Webhooks are now available for batched PR merges in Merge Queue. This allows you to build custom automations and respond to events when batching is enabled.

### April 2025

**April 17, 2025**

**[Merge Queue: updateQueue API](https://docs.trunk.io/changelog/2025-04-17-merge-queue-updatequeue-api.md)**

We’ve added a new updateQueue API to Trunk Merge Queue that enables you to update a Merge Queue’s state.

### January 2025

**January 28, 2025**

**[Merge: Webhook notifications for Microsoft Teams and Slack](https://docs.trunk.io/changelog/2025-01-28-merge-webhook-notifications-for-microsoft-teams-and-slack.md)**

We're excited to share our new webhook integrations for Trunk Merge. You can now send notifications about events in the merge queue to your Microsoft Teams and Slack channels.

## 2024

### July 2024

**July 17, 2024**

**[Merge Queue: New metrics dashboard](https://docs.trunk.io/changelog/2024-07-17-trunk-merge-queue-metrics-dashboard.md)**

Merge queues are integral to validating and merging PRs - a critical part of any development process. Minimizing the friction to merge a PR and ensuring the merging process remains fast is essential…

**July 10, 2024**

**[Merge Queue: API updates](https://docs.trunk.io/changelog/2024-07-10-trunk-merge-queue-public-api-updated.md)**

Trunk Merge Queue has added more functionality to its public API, allowing it to fit seamlessly into any integration.

### May 2024

**May 26, 2024**

**[Merge Queue: Draft PR support](https://docs.trunk.io/changelog/2024-05-26-testing-using-draft-prs.md)**

Trunk Merge Queue, by default, will now raise draft pull requests in order to test changes submitted to the merge queue! Trunk Merge Queue is now even easier to get started with and no longer…

**May 17, 2024**

**[Merge Queue: First class Nx support](https://docs.trunk.io/changelog/2024-05-17-first-class-support-for-trunk-merge-queue-nx.md)**

Trunk Merge Queue, through its Parallel Queues feature, can dynamically create new merge queues to test only the pull requests with potential conflicts together.

### April 2024

**April 5, 2024**

**[Merge Queue: Batching support](https://docs.trunk.io/changelog/2024-04-05-merge-batching-support.md)**

Trunk Merge Queue now supports grouping PRs into batches for greater throughput. See Batching docs for more details.

**April 5, 2024**

**[Merge Queue: Webhook support](https://docs.trunk.io/changelog/2024-04-05-merge-web-hook-support.md)**

Trunk Merge Queue now supports webhooks to provide realtime events to integrated platforms. See the Webhooks API doc for more details.

### March 2024

**March 29, 2024**

**[Merge Queue: Optimistic merging and pending failure depth](https://docs.trunk.io/changelog/2024-03-29-optimistic-merging-and-pending-failure-depth.md)**

Merge Queue now supports Optimistic Merging to allow failed tests to be merged if later PRs pass. Merge Queue also now supports Pending Failure Depth to allow failed tests to remain in the queue for…

**March 15, 2024**

**[Merge Queue: PR prioritization](https://docs.trunk.io/changelog/2024-03-15-trunk-merge-pr-prioritization.md)**

Support for setting the priority of a pull request from the command line or a GitHub comment. Higher priority PRs will move ahead of lower priority PRs. See PR Prioritization docs for more details.

### February 2024

**February 20, 2024**

**[Merge Queue : Support for forked and open source repos](https://docs.trunk.io/changelog/2024-02-20-merge-support-for-forked-and-open-source-repos.md)**

Trunk Merge Queue now supports uploading impacted targets from forked PRs, and has more verbose information on PRs for contributors that aren't a part of the same Trunk org.

### January 2024

**January 12, 2024**

**[Merge Queue: Automatic status checks](https://docs.trunk.io/changelog/2024-01-12-merge-automatic-status-checks.md)**

Trunk Merge Queue now supports automatically setting the required status checks by scanning the GitHub branch protection of the target branch. See Define Required Status For Testing for details.

## 2023

### November 2023

**November 21, 2023**

**[Trunk Merge Queue - Parallel Queues](https://docs.trunk.io/changelog/2023-11-21-trunk-merge-parallel-queues.md)**

Trunk Merge Queue now offers two modes for creating merge queues: "Single" and "Parallel". The Single mode operates as a standard first-in, first-out merge queue, where pull requests (PRs) are added…
