Skip to content

docs: correct the consumer table #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
unional wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: correct the consumer table #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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`
Expand Down Expand Up @@ -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
Expand Down