From e3c7c40ba25b747eafe3b02ee927b393295fa90c Mon Sep 17 00:00:00 2001 From: Abhinav Prakash Date: Sat, 3 Oct 2026 20:56:01 +0530 Subject: [PATCH] docs: correct stale dep-lockstep bullet and test annotation (#4924) Signed-off-by: Abhinav Prakash --- AGENTS.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 3ab3b6434a..d4f04abe9e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -100,7 +100,7 @@ dependencies are managed with **`uv`, never `pip`**. # TypeScript: one install at the root covers all four workspaces npm install npm run build # every workspace -npm test -w src/ # one workspace (vitest, with coverage) +npm test -w src/ # one workspace (vitest) # Python: per server cd src/ @@ -177,8 +177,8 @@ than `GITHUB_TOKEN`. Today that is `release.yml`'s publish jobs and upward escape by silently downgrading. - **When you bump a devDependency that several TypeScript workspaces declare** (`typescript`, `vitest`, `@vitest/coverage-v8`, `@types/node`, …), bump it in - every workspace that declares it. Their ranges already differ; do not widen the - skew. + every workspace that declares it. Declare it with one identical range + everywhere — the `verify:dep-lockstep` guard enforces this. - **A Python dependency change updates that server's `uv.lock`** in the same commit (`uv lock`). CI installs with `--frozen` / `--locked` and fails on a stale lockfile.