Skip to content

docs: update stale dep-lockstep bullet and npm test annotation (#4924) #4956

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

Closed
AbhiPra24 wants to merge 1 commit into from
+3 −3
Closed

docs: update stale dep-lockstep bullet and npm test annotation (#4924) #4956

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 AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/<server> # one workspace (vitest, with coverage)
npm test -w src/<server> # one workspace (vitest)

# Python: per server
cd src/<server>
Expand Down Expand Up @@ -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.
Expand Down
Loading