Skip to content

Commit fc1307d

Browse files
cliffhallclaude
andcommitted
docs(agents): state the dep-lockstep rule the guard enforces
The Dependencies bullet said shared devDependency ranges "already differ; do not widen the skew". Since modelcontextprotocol#4864, verify:dep-lockstep (in validate:guards, so in CI) requires one identical range everywhere a SHARED_DEV_DEPENDENCIES package is declared. State that rule and name the guard. The issue's second item, the "with coverage" annotation on npm test, was already fixed by f149a2a. Refs modelcontextprotocol#4924 Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent b0d865d commit fc1307d

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎AGENTS.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -181,8 +181,9 @@ than `GITHUB_TOKEN`. Today that is `release.yml`'s publish jobs and
181181
upward escape by silently downgrading.
182182
- **When you bump a devDependency that several TypeScript workspaces declare**
183183
(`typescript`, `vitest`, `@vitest/coverage-v8`, `@types/node`, …), bump it in
184-
every workspace that declares it. Their ranges already differ; do not widen the
185-
skew.
184+
every workspace that declares it, with one identical range everywhere. The
185+
`verify:dep-lockstep` guard (in `validate:guards`, so in CI) fails when two
186+
declarations of a package in its `SHARED_DEV_DEPENDENCIES` list differ.
186187
- **A Python dependency change updates that server's `uv.lock`** in the same
187188
commit (`uv lock`). CI installs with `--frozen` / `--locked` and fails on a
188189
stale lockfile.

0 commit comments

Comments
 (0)