From 0f97396bcae261d684802584fe10f2f9fc93c3c8 Mon Sep 17 00:00:00 2001 From: unional Date: Wed, 12 Aug 2026 23:29:21 -0700 Subject: [PATCH] docs: correct the consumer table MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit rolldown-inline-type-exports was listed as a consumer of this repo. It is not — it consumes unional/.github, whose workflows share these filenames. The original survey matched on workflow filename rather than owner. Four repos consume these workflows, not five: repobuddy (CLI v3, @v2) and storybook, visual-testing, jest-watch-toggle-config-2 (CLI v2, @v1). Co-Authored-By: Claude Opus 5 --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index da4f5e8..106a71e 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,8 @@ If you need a ref that never moves under you, pin the exact version instead Do **not** pin `@main`. `main` is the development branch: it carries unreleased and possibly broken work, and every consumer on it takes every change the -instant it merges. That is how a silently-broken release path reached five repos +instant it merges. That is how a silently-broken release path reached all four +consumers at once ([#43](https://github.com/repobuddy/.github/issues/43)). ### Why there are two lines @@ -68,7 +69,6 @@ lines exist in parallel rather than one being a migration deadline: | `repobuddy/repobuddy` | `^3.0.0` | `@v2` | | `repobuddy/storybook` | `^2.29.7` | `@v1` | | `repobuddy/visual-testing` | `^2.29.8` | `@v1` | -| `repobuddy/rolldown-inline-type-exports` | `^2.29.8` | `@v1` | | `repobuddy/jest-watch-toggle-config-2` | `^2.25.2` | `@v1` | **Branch layout:** `main` is the v1 line. The v2 line lives on the `v2.x` @@ -130,7 +130,7 @@ actually excluding majors is a separate defect and should be fixed on its own. Not `v0.x`. Two reasons: -1. These workflows are already in production use by five repos and have been +1. These workflows are already in production use by four repos and have been for a long time. `v0.x` would advertise "expect this to break", which is a less honest description of the status quo than `v1` — and `@main` offered no stability guarantee whatsoever, so anything we tag is an improvement rather