chore(deps): update minor and patch dependencies - #294
Merged
Merged
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refreshes the AgentsKit runtime dependencies and
@types/nodeto their latest minor/patch releases, regeneratingpackage-lock.json— the lockfile CI consumes vianpm ci.@agentskit/adapters^0.12.2^0.17.0@agentskit/core^1.9.0^1.12.9@agentskit/ink0.10.90.10.11@agentskit/runtime^0.7.3^0.10.17@agentskit/tools^0.9.4^0.13.8zod^4.6.1^4.6.5@types/node^22.10.0^22.20.3@changesets/climoves3.0.2→3.0.3in the lockfile only: the declared range already covers it, andtest/documentation.test.mjspins the range string as part of the release contract.Held back:
@agentskit/doc-bridgeStays at
1.7.45. Its 1.10.0 release deliberately moves body text out ofknowledge[]and into the projection:test/documentation.test.mjssearchesindex.knowledge[].bodyfor 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.1range is untouched and the lockfile keeps the resolution it already had, soak-docs gate runstill reportsIndex is freshagainst the committed.doc-bridge/index.json— verified directly.README Standard
package.jsonis a README Standard v1 freshness source, socode-review-root'ssourceHashis refreshed withnpm run readme:standard:refresh.reviewedOn/reviewDueOnare untouched.Verification
Run in a clean worktree off
mainwith freshnode_modules— the exact CI sequence:npm run check→typechecknpm run check→testnpm run check→docs:gatellms-fullin sync, 12/12 documentation testsnpm run check→dist/src/cli.js --helpnpm run check→check:readme-standardnpm pack --dry-run🤖 Generated with Claude Code
https://claude.ai/code/session_015eDrUXwb4BZWXUuwpNMkDn
Generated by Claude Code