From d329ee485fa4428cc7d0d3d6e351b668ef8f2b8a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 29 Jun 2026 20:47:15 +0000 Subject: [PATCH 1/6] fix: correct frontmatter date and nav entry for browser extension 0.13.0 changelog --- changelog/2026-06-29-browser-extension-0-13-0.mdx | 6 +++--- docs.json | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/changelog/2026-06-29-browser-extension-0-13-0.mdx b/changelog/2026-06-29-browser-extension-0-13-0.mdx index e2d3d1e2..86cf99c8 100644 --- a/changelog/2026-06-29-browser-extension-0-13-0.mdx +++ b/changelog/2026-06-29-browser-extension-0-13-0.mdx @@ -1,9 +1,9 @@ --- title: "Browser Extension: Performance and Bug Fixes" description: "The Trunk browser extension 0.13.0 ships performance improvements and bug fixes." -date: "null" -category: "Browser Extension" -type: "update" +date: 2026-06-29 +category: Browser Extension +type: update --- **Version 0.13.0 of the Trunk browser extension is now available with performance improvements and bug fixes.** diff --git a/docs.json b/docs.json index 641ccd6e..37e3fce6 100644 --- a/docs.json +++ b/docs.json @@ -624,7 +624,7 @@ { "group": "June", "pages": [ - "changelog/2026-06-29-browser-extension-0-13-0.mdx", + "changelog/2026-06-29-browser-extension-0-13-0", "changelog/2026-06-18-merge-queue-stale-tab-refresh-fix", "changelog/2026-06-17-flaky-tests-browser-extension-failure-details", "changelog/2026-06-17-merge-queue-metrics-and-extension-updates", From aadae6a2fb04293631f1e27847cf8cc368992e7e Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 29 Jun 2026 20:49:41 +0000 Subject: [PATCH 2/6] fix: remove stray space before colon in browser extension changelog title --- changelog/2026-06-29-browser-extension-0-13-0.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelog/2026-06-29-browser-extension-0-13-0.mdx b/changelog/2026-06-29-browser-extension-0-13-0.mdx index fff71fb6..ac51204e 100644 --- a/changelog/2026-06-29-browser-extension-0-13-0.mdx +++ b/changelog/2026-06-29-browser-extension-0-13-0.mdx @@ -1,5 +1,5 @@ --- -title: "Browser Extension : Performance and bug fixes" +title: "Browser Extension: Performance and bug fixes" description: "The Trunk browser extension 0.13.0 ships performance improvements and bug fixes." date: 2026-06-29 category: Browser Extension From 26c689d67573bb5f4745ef32594eb88f3990b519 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 1 Jul 2026 15:56:14 +0000 Subject: [PATCH 3/6] fix: remove misplaced comma between subject and verb in quarantining note --- flaky-tests/get-started/ci-providers/github-actions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/flaky-tests/get-started/ci-providers/github-actions.mdx b/flaky-tests/get-started/ci-providers/github-actions.mdx index 015edba4..9e69bef9 100644 --- a/flaky-tests/get-started/ci-providers/github-actions.mdx +++ b/flaky-tests/get-started/ci-providers/github-actions.mdx @@ -132,7 +132,7 @@ You can quarantine flaky tests by wrapping the test command or as a follow-up st -Using the Trunk Analytics Uploader Action in your GitHub Actions Workflow files, may need modifications to your workflow files to support quarantining. +Using the Trunk Analytics Uploader Action in your GitHub Actions Workflow files may need modifications to your workflow files to support quarantining. If you upload your test results as a second step after you run your tests, **you need to add** `continue-on-error: true` **on your test step so your CI** job will continue even on failures. From ad264dce9f654b19c538088f1487f57e31caf99f Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 6 Jul 2026 17:03:00 +0000 Subject: [PATCH 4/6] fix: correct subject-verb agreement in draft PR mode bullet --- merge-queue/getting-started/configure-branch-protection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/merge-queue/getting-started/configure-branch-protection.mdx b/merge-queue/getting-started/configure-branch-protection.mdx index 273291ef..1b7be8c4 100644 --- a/merge-queue/getting-started/configure-branch-protection.mdx +++ b/merge-queue/getting-started/configure-branch-protection.mdx @@ -42,7 +42,7 @@ When a pull request enters the queue, Trunk creates a draft pull request to test Things to look out for: * This mode also creates a `trunk-merge/` branch -* Trunk automatically closes the draft PRs and merge the original PRs +* Trunk automatically closes the draft PRs and merges the original PRs **When to use a different approach:** If you have expensive preview deployments, review-only workflows, or security scans that you don't want running during merge queue testing, consider Push-triggered mode instead. From 58b1a7b8723b4f0e64857619587fb0756f7cd16d Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 22 Jul 2026 14:33:30 +0000 Subject: [PATCH 5/6] fix: remove duplicated "both" in dependabot and renovate FAQ answer --- merge-queue/reference/common-problems.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/merge-queue/reference/common-problems.mdx b/merge-queue/reference/common-problems.mdx index 1d76332a..01d83496 100644 --- a/merge-queue/reference/common-problems.mdx +++ b/merge-queue/reference/common-problems.mdx @@ -136,7 +136,7 @@ og:title: "Trunk Merge Queue FAQ" - By default, both [dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#changing-the-rebase-strategy-for-dependabot-pull-requests) and [renovate](https://docs.renovatebot.com/updating-rebasing/#updating-and-rebasing-branches) both will rebase their PRs whenever other PRs merge into their base branch. If that rebase happens when those PRs are in the queue, they will get kicked since they were updated. There are two ways to mitigate this: + By default, both [dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#changing-the-rebase-strategy-for-dependabot-pull-requests) and [renovate](https://docs.renovatebot.com/updating-rebasing/#updating-and-rebasing-branches) will rebase their PRs whenever other PRs merge into their base branch. If that rebase happens when those PRs are in the queue, they will get kicked since they were updated. There are two ways to mitigate this: 1. Both dependabot and renovate can be configured to not automatically rebase, while renovate can specifically be configured to only rebase if there's a merge conflict ([dependabot](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy), [renovate](https://docs.renovatebot.com/configuration-options/#rebasewhen)) 2. Their PRs can be manually merged, and anything currently in the merge queue will restart with those merged changes From 78869b6f51daf557cafd90a25d4052f5ac9e6cb0 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 24 Jul 2026 18:58:57 +0000 Subject: [PATCH 6/6] fix: remove stray space before period in flaky test broadcast step --- flaky-tests/management/managing-detected-flaky-tests.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/flaky-tests/management/managing-detected-flaky-tests.mdx b/flaky-tests/management/managing-detected-flaky-tests.mdx index de08af61..4605812f 100644 --- a/flaky-tests/management/managing-detected-flaky-tests.mdx +++ b/flaky-tests/management/managing-detected-flaky-tests.mdx @@ -44,7 +44,7 @@ Creating Linear or Jira tickets for detected flaky tests helps to integrate flak ### Step 3: Broadcast flakes -It is important to keep the team informed on all status changes for flaky tests . This allows for fast follow-up when a test is marked as flaky. +It is important to keep the team informed on all status changes for flaky tests. This allows for fast follow-up when a test is marked as flaky. * Use the [built-in Slack or Microsoft Teams webhook integrations](../webhooks/) to transform webhook payloads into messages. * Trunk's built-in templates help you get started and test the connection.