[close - superseded by #27] docs: draft weekly changelog for flaky tests updates

.mintignore

@@ -9,6 +9,7 @@
 drafts/
 *.draft.mdx
 _deprecated/
+changelog/
 
 # Inactive products (kept in source for future use, hidden from build)
 

changelog/2026-05-18-flaky-tests-failure-count-monitor.mdx

@@ -0,0 +1,21 @@
+---
+title: "Flaky Tests: Failure Count Monitor"
+description: "Flag tests the moment they accumulate a configured number of failures on monitored branches."
+date: 2026-05-18
+category: Flaky Tests
+type: new-feature
+---
+
+**You can now flag tests as soon as they accumulate a configured number of failures — no failure-rate math, no minimum sample size required.**
+
+The new **failure count monitor** reacts to individual failures within a rolling time window, making it well-suited for stable branches like `main` where any single failure is meaningful. Set it up with a failure count (default: 1), a window, a resolution timeout, and the branches to watch.
+
+Common uses:
+
+- **Stable branch alerting** — flag any test that fails on `main`, even once.
+- **Post-merge regression detection** — catch regressions before a failure-rate monitor accumulates enough data to trigger.
+- **Merge queue / release branches** — quick alerting on branches where failures are suspicious by definition.
+
+A live **Preview** panel shows which tests would be flagged under your current settings before you save, so you can tune the threshold with confidence.
+
+[Read the docs](https://docs.trunk.io/flaky-tests/detection/failure-count-monitor) to learn more.

changelog/2026-05-18-flaky-tests-monitor-label-actions.mdx

@@ -0,0 +1,18 @@
+---
+title: "Flaky Tests: Apply Labels from Monitors"
+description: "Monitors can now apply labels to tests instead of classifying them as flaky or broken."
+date: 2026-05-18
+category: Flaky Tests
+type: update
+---
+
+**Monitors can now apply labels to tests instead of changing their health status.** This is useful when you want a monitor to surface a pattern for triage without marking tests flaky or broken — and it doubles as a dry-run while you tune a new monitor.
+
+When you create or edit a [pass-on-retry](https://docs.trunk.io/flaky-tests/detection/pass-on-retry-monitor), [failure rate](https://docs.trunk.io/flaky-tests/detection/failure-rate-monitor), or [failure count](https://docs.trunk.io/flaky-tests/detection/failure-count-monitor) monitor, the **Action** section now offers:
+
+- **Classify test status** (default) — the original behavior; the test is marked flaky or broken while the monitor is active.
+- **Apply labels** — one or more labels are added to the test while the monitor is active, with no change to the test's health status.
+
+By default, monitor-applied labels are removed when the monitor resolves; you can turn that off to keep the labels on the test. When the same label is applied by multiple sources (a user, multiple monitors, or both), it stays on the test until every source removes it.
+
+[Read the docs](https://docs.trunk.io/flaky-tests/management/test-labels#automatic-labeling-from-monitors) to learn more.

changelog/2026-05-18-flaky-tests-test-labels.mdx

@@ -0,0 +1,19 @@
+---
+title: "Flaky Tests: Organization-Scoped Test Labels"
+description: "Tag, organize, and filter your test suite with org-wide labels."
+date: 2026-05-18
+category: Flaky Tests
+type: new-feature
+---
+
+**Test labels are now generally available — organize, categorize, and filter your test suite with org-scoped tags.**
+
+Create labels with a name, description, and color at **Settings > Organization > Test Labels**. Then:
+
+- **Apply labels manually** from the test detail page. Each assignment records who applied it and when.
+- **Filter the tests list** by label to slice your suite by the categories your team cares about (owning team, area of the product, risk level, etc.).
+- **Search labels inline** when applying, or create a new one on the fly without leaving the test detail page.
+
+Deleting a label removes it from every test it's applied to. Labels referenced by a monitor's [label action](https://docs.trunk.io/flaky-tests/management/test-labels#automatic-labeling-from-monitors) can't be deleted until those references are cleared, so monitor configuration stays consistent.
+
+[Read the docs](https://docs.trunk.io/flaky-tests/management/test-labels) to learn more.