Skip to content

docs(agents): state the dep-lockstep rule the guard enforces #5051

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

Merged
cliffhall merged 1 commit into from
Oct 5, 2026
Merged

docs(agents): state the dep-lockstep rule the guard enforces #5051

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
5 changes: 3 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,8 +181,9 @@ 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, with one identical range everywhere. The
`verify:dep-lockstep` guard (in `validate:guards`, so in CI) fails when two
declarations of a package in its `SHARED_DEV_DEPENDENCIES` list differ.
- **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