release: v0.1.1225 - #3522
Merged
Merged
release: v0.1.1225#3522
Conversation
kojiwakayama
enabled auto-merge
August 9, 2026 22:27
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe release version changes from ChangesRelease version
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 9, 2026
Closed
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.
Patch release cutting #3521, and carrying #3519 from v0.1.1224.
Contents
fix(openai): bound tool-call arguments by bytes, not provider chunking (#3521) — fixes veryfront-issue-inbox#432
Every scheduled tick of
agentic-job-submission-processingwas producing a failed child run:invalid successful stream (tool call arguments exceeded 4096 fragments). The parent reportedcompletedwhile the child died, so it was invisible from run status.appendOpenAIStreamToolArgumentcounted every fragment against the 4096 cap, including ones carrying bytes. At typical 5–20 byte deltas that is ~20–80 KB — roughly 2–8% of the 1 MiB the byte budget nominally allows — so the fragment cap always fired first and the byte limit was unreachable. Fragment count is chosen by the provider's tokenizer, not the caller, so the same tool call passed or failed on chunking alone.Both provider streams' existing tests show what the cap is for: each floods empty deltas. Zero-byte fragments never advance the byte budget, so they are the only ones that can arrive unbounded — and now the only ones counted. Both flood tests still trip the cap unchanged.
feat(agent): stamp an absolute
emittedAton persisted run events (#3519)Already published as v0.1.1224 but not promoted; it ships here instead so production takes one rollout rather than two.
elapsedMsis anchored to encoder construction, so its meaning depends on which encoder produced it — the ambiguity behind three of the four attempts to landelapsedMs.emittedAthas no anchor. Both are kept: a wall clock can step backwards under NTP, a monotonic reading cannot.Includes the refactor forwarding encoder timing as one
timingoptions object rather than re-declaring each clock through four wrapper layers.Version files
deno.json,src/utils/version-constant.ts,src/html/hydration-script-builder/hydration-runtime.generated.ts— all three at 0.1.1225.Cut with
--no-test --no-build;--no-buildremains mandatory until issue #435 (deno task verify:distdoes not exist).Summary by CodeRabbit