chore(repo): version packages - #502
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 6, 2026 20:09
1b25ae8 to
1043e26
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 7, 2026 07:55
1043e26 to
c0751dc
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
evlog@2.25.0
Minor Changes
#501
16d5323Thanks @HugoRCD! - Cover the eve 0.30 event surface.evlog/evenow requires eve >= 0.30 — the peer range moves from>=0.24.3. The eve integration is still beta and its peer floor moves with it, so this ships as a minor; nothing outsideevlog/eveis affected. Agents on an older eve keep working on the previous evlog — upgrade eve first.The wide event now carries what eve started reporting since 0.24:
eve.runtime— eve version, agent id, model, and the deployed git sha, branch and date, fromsession.startedeve.parent— parent and root session ids for a subagent run, so a drain can rebuild the delegation treeeve.authorizations— connection sign-ins with their outcome, reason and duration; a turn parked on one ends aseve.phase: 'awaiting-authorization'eve.compaction— how many compactions ran, on which model, and how full the context was when the first one triggeredeve.contextCleared,eve.stepFailuresandeve.failedSteps— a model call that failed and was retried no longer disappears from a turn that ends up succeedingai.costUsd— the cost eve reports, used in place of thecostpricing map when available.ai.modelfalls back to the model reported at session start, somodelis only needed for dynamic-model agentsdurationMsand astartedstatusmessagereplacesredactMessagewith three modes:'omit'(default),'preview'(text truncated tomessagePreviewLength, attachments reduced to their type and media type) and'full'. Attachment parts were previously not redacted at all.redactMessagestill works and is deprecated.sessionEvent: trueadds one wide event per session on top of the per-turn ones, rolling up turns, tokens, cost, tools used, compactions and authorizations — one row per conversation, which is what makes tail sampling useful on an agent.#506
f8fb677Thanks @HugoRCD! - Close the remaining gaps in the eve integration, and adddefineEvlogInstrumentation().A wide event and an Agent Runs span describe the same turn, but nothing joined them: you could not jump from a trace in Braintrust, Datadog or the Vercel dashboard to the event in your drain. Export the new definition from
agent/instrumentation.tsand every model-call span carriesevlog.request_idandevlog.session_id, the values the wide event reports asrequestIdandeve.sessionId:Without
setup, OpenTelemetry export is untouched and eve keeps writing its local traces.functionId,recordInputs,recordOutputsandtraceChannelRequestspass through to eve.Three more of eve's stream events now reach the wide event:
eve.reasoning—blocksandchars, the size of the model's thinking. The reasoning text itself is never recorded.message.responseChars, andmessage.responseoncemessageis'preview'or'full'— the agent's answer, following the same rule as the incoming message.eve.result— the structured result of an agent with an output schema.Patch Changes
#500
8ffba92Thanks @HugoRCD! - Emit a wide event for eve turns that end withoutturn.completedorturn.failed.A turn cancelled by eve produced no wide event, and its logger, accumulator and session slot stayed in memory for good: LRU eviction skips any session that still has an active turn, so nothing ever reclaimed them.
turn.cancellednow closes the turn on its own terminal path — status499,eve.phase: 'cancelled', levelinfo, because cancellation is not a failure in eve's model.session.failedandsession.completedflush any turn still open for that session and drop its carried-over context, which also ends the indefinite retention of snapshots for finished sessions.@evlog/cli@0.5.1
Patch Changes
16d5323,f8fb677,8ffba92]: