Skip to content

chore(deps): update minor and patch dependencies - #294

Merged
EmersonBraun merged 1 commit into
mainfrom
claude/deps-minor-patch
Sep 16, 2026
Merged

EmersonBraun merged 1 commit into
mainfrom
claude/deps-minor-patch

Conversation

@EmersonBraun

Copy link
Copy Markdown
Member

What

Refreshes the AgentsKit runtime dependencies and @types/node to their latest minor/patch releases, regenerating package-lock.json — the lockfile CI consumes via npm ci.

Package From To
@agentskit/adapters ^0.12.2 ^0.17.0
@agentskit/core ^1.9.0 ^1.12.9
@agentskit/ink 0.10.9 0.10.11
@agentskit/runtime ^0.7.3 ^0.10.17
@agentskit/tools ^0.9.4 ^0.13.8
zod ^4.6.1 ^4.6.5
@types/node ^22.10.0 ^22.20.3

@changesets/cli moves 3.0.23.0.3 in the lockfile only: the declared range already covers it, and test/documentation.test.mjs pins the range string as part of the release contract.

Held back: @agentskit/doc-bridge

Stays at 1.7.45. Its 1.10.0 release deliberately moves body text out of knowledge[] and into the projection:

knowledge[] keeps every reader that predates the projection working: the curated sidecars first, in reading order, then every projected document and module. Body text lives once, in the projection, so a projected index carries no bodies here.

test/documentation.test.mjs searches index.knowledge[].body for the ecosystem product names and routes, so a regenerated index fails that assertion. Teaching those readers the projection layout is its own change, not a dependency refresh. The declared ^1.1.1 range is untouched and the lockfile keeps the resolution it already had, so ak-docs gate run still reports Index is fresh against the committed .doc-bridge/index.json — verified directly.

README Standard

package.json is a README Standard v1 freshness source, so code-review-root's sourceHash is refreshed with npm run readme:standard:refresh. reviewedOn / reviewDueOn are untouched.

Verification

Run in a clean worktree off main with fresh node_modules — the exact CI sequence:

Check Result
npm run checktypecheck clean
npm run checktest 311/311 passing
npm run checkdocs:gate index fresh, conformance pass, llms-full in sync, 12/12 documentation tests
npm run checkdist/src/cli.js --help ok
npm run checkcheck:readme-standard PASS (1 surface)
npm pack --dry-run ok, 162 files

🤖 Generated with Claude Code

https://claude.ai/code/session_015eDrUXwb4BZWXUuwpNMkDn


Generated by Claude Code

Refresh the AgentsKit runtime dependencies and @types/node to their
latest minor/patch releases, regenerating package-lock.json (the lockfile
CI consumes via `npm ci`).

- @agentskit/adapters ^0.12.2 -> ^0.17.0
- @agentskit/core     ^1.9.0  -> ^1.12.9
- @agentskit/ink      0.10.9  -> 0.10.11
- @agentskit/runtime  ^0.7.3  -> ^0.10.17
- @agentskit/tools    ^0.9.4  -> ^0.13.8
- zod                 ^4.6.1  -> ^4.6.5
- @types/node         ^22.10.0 -> ^22.20.3

@agentskit/doc-bridge is deliberately held at 1.7.45. Its 1.10.0 release
moves body text out of `knowledge[]` and into the projection, so a
regenerated index no longer satisfies test/documentation.test.mjs, which
searches `index.knowledge[].body` for the ecosystem product names and
routes. Adapting those readers to the projection layout is its own
change, not a dependency refresh; the declared `^1.1.1` range is
unchanged and the lockfile keeps the resolution it already had.
@changesets/cli moves 3.0.2 -> 3.0.3 in the lockfile only, since the
declared range already covers it and the release contract test pins the
range string.

package.json is a README Standard v1 freshness source, so the
code-review-root sourceHash is refreshed via
`npm run readme:standard:refresh`; reviewedOn/reviewDueOn are untouched.

Verified locally: `npm run check` (typecheck, 311/311 node:test, docs
gate, CLI smoke, README Standard) and `npm pack --dry-run` both clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015eDrUXwb4BZWXUuwpNMkDn
@EmersonBraun
EmersonBraun merged commit 45bd92b into main Sep 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants