Skip to content

Commit e3c7c40

Browse files
committed
docs: correct stale dep-lockstep bullet and test annotation (#4924)
Signed-off-by: Abhinav Prakash <[email protected]>
1 parent 2b02c01 commit e3c7c40

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎AGENTS.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ dependencies are managed with **`uv`, never `pip`**.
100100
# TypeScript: one install at the root covers all four workspaces
101101
npm install
102102
npm run build # every workspace
103-
npm test -w src/<server> # one workspace (vitest, with coverage)
103+
npm test -w src/<server> # one workspace (vitest)
104104

105105
# Python: per server
106106
cd src/<server>
@@ -177,8 +177,8 @@ than `GITHUB_TOKEN`. Today that is `release.yml`'s publish jobs and
177177
upward escape by silently downgrading.
178178
- **When you bump a devDependency that several TypeScript workspaces declare**
179179
(`typescript`, `vitest`, `@vitest/coverage-v8`, `@types/node`, …), bump it in
180-
every workspace that declares it. Their ranges already differ; do not widen the
181-
skew.
180+
every workspace that declares it. Declare it with one identical range
181+
everywhere — the `verify:dep-lockstep` guard enforces this.
182182
- **A Python dependency change updates that server's `uv.lock`** in the same
183183
commit (`uv lock`). CI installs with `--frozen` / `--locked` and fails on a
184184
stale lockfile.

0 commit comments

Comments
 (0)