chore: update changelog

Author: mergify-ci-bot

src/content/changelog/2026-01-19-add-ability-for-retry-rules-to-retry-entire-pipelines.mdx

@@ -0,0 +1,11 @@
+---
+title: "Add ability for retry rules to retry entire pipelines"
+date: 2026-01-19
+tags:
+  - CI Insights
+description: "Allow users to retry rules by choosing the retry mode"
+---
+
+A new option named `retry mode` has been added to the configuration page of `retry rules`.
+
+This option introduce the ability to choose the retry mode of the retry rules, retrying either the failed jobs or the entire pipeline.

src/content/changelog/2026-03-17-time-binned-merge-queue-checks-outcome-endpoint.mdx

@@ -0,0 +1,16 @@
+---
+title: "Time-binned merge queue checks outcome endpoint"
+date: 2026-03-17
+tags:
+  - Merge Queue
+  - API
+description: "New API endpoint to track dequeue reasons over time as a time-series graph"
+---
+
+New API endpoint `GET /v1/repos/{owner}/{repository}/stats/queues_checks_outcome_count` that returns dequeue reason counts grouped by time intervals.
+
+The existing `merge_queue_checks_outcome` endpoint only returns aggregate totals (useful for pie charts). This new endpoint enables time-series graphs showing how dequeue reasons (e.g. CHECKS_FAILED, MERGE_QUEUE_RESET, SUCCESS) evolve over time. The old endpoint is now deprecated.
+
+Supports filtering by base branch, partition, queue name, and priority rule.
+
+PR: [https://github.com/Mergifyio/engine/pull/27098](https://github.com/Mergifyio/engine/pull/27098)

src/content/changelog/2026-03-18-deprecation-of-post-check-action.mdx

@@ -0,0 +1,14 @@
+---
+title: "Deprecation of `post_check` action"
+date: 2026-03-18
+tags:
+  - Deprecations
+  - Merge Protections
+description: "Automatic migration of post_check actions to merge_protections entries"
+---
+
+The `post_check` action in `pull_request_rules` is being replaced by `merge_protections`. A new transformer handles the migration automatically:
+
+## What you need to do
+
+The transformer runs automatically and will open a pull request with the required changes. However, we recommend reviewing your configuration and migrating to `merge_protections` explicitly, as the `post_check` action will be removed in a future release.

src/content/changelog/2026-03-20-merge-queue-pr-exit-reasons-and-idle-time-breakdown-in-stats.mdx

@@ -0,0 +1,22 @@
+---
+title: "Merge Queue: PR exit reasons and idle time breakdown in stats"
+date: 2026-03-20
+tags:
+  - Merge Queue
+description: "New stats endpoints for the merge queue dashboard: PR exit reasons count (unique PRs by final exit reason) and idle time breakdown (capacity, schedule, freeze). Powers the new Sankey flow diagram and stacked time chart."
+---
+
+Two new stats capabilities for the merge queue dashboard:
+
+**PR Exit Reasons**
+
+New visualization showing how pull requests flow through your merge queue — see at a glance how many PRs were merged successfully, cancelled, or failed, broken down over time. This powers the new Sankey flow diagram on the dashboard.
+
+**Idle Time Breakdown**
+
+Queue time stats now break down idle time into actionable categories:
+
+- **Capacity** — time spent waiting because the queue was at max parallel checks
+- **Schedule** — time spent waiting due to merge schedule restrictions
+- **Freeze** — time spent waiting because the queue was frozen
+This helps you understand where your merge queue time is actually spent and what to optimize.