chore(deps): bump weave to 0.16.6 - #169
Merged
Merged
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 14, 2026
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
rgao-coreweave
force-pushed
the
bump-weave-0.16.5
branch
from
August 14, 2026 18:57
6be62b6 to
6147797
Compare
HiveMind Sessions1 session · 4m · $2.55
View all sessions in HiveMind → Run |
ro31337
approved these changes
Aug 17, 2026
ro31337
left a comment
There was a problem hiding this comment.
Reviewed: dependency artifact, compatibility, and checks verified. No blockers.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

Bumps
weavefrom^0.16.3to^0.16.6. Dependency only, no code change.What is new, and what we use
Diffed the published
distacross 0.16.3 → 0.16.5 → 0.16.6 rather than trusting changelogs. 0.16.6 is by far the larger of the two releases.Adopted at the top of this stack
Turn.record({ outputMessages })(0.16.5) andSubAgent.record({ messages, outputMessages })(0.16.6). The SubAgent half is what makes the migration complete rather than partial, so all fivegen_ai.output.messageswriters move together.Available, not adopted here
Tool.end({ result, errorType })andargs?: JsonObject | string. 0.16.6 deprecates thetool.result =setter, which we use at three sites incallLifecycle.ts. Still functional, so this is a follow-up rather than a blocker. Flagged below.JsonValue/JsonObjectexported types. We already define our own incallLifecycle.ts.opLinkSpanProcessor,evalLinkSpanProcessorchanges. Eval/op linking, not used here.Not applicable
flush()/client.flush()/pendingCallCount()/useCallsComplete: classic Weave calls batch path. We emit only OTel genai spans and already useflushOTel().registerCustomRuntime()+CustomRuntimeId: custom inference-runtime registration.WEAVE_INTEGRATION_NAME/_VERSION/_META_PREFIXsemconv consts: not exported from the public entrypoint (only via a deep internal import). The strings we hand-roll ingenaiSpans.tsalready match the canonical values exactly, so they are now upstream-validated.Follow-up worth filing
tool.result =is deprecated in favour ofend({ result }), andend()now takeserrorTypewhich maps toerror.type(we set that attribute by hand). Happy to send that as a fourth PR on this stack.Verification
tsc clean, 203/203 tests pass.
🤖 Generated with Claude Code