Cut changelog for 0.2.107 - #592
Merged
Merged
Conversation
TheGreatAxios
enabled auto-merge
August 24, 2026 04:18
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
1 participant
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.
Ten merges since v0.2.106. Entries were backfilled — none of the ten PRs added one, same as last release.
Agent — oversized tool output spills into the committed blob store with a working
tool-output:///handle (CL-6965) · static per-director write-path allowlist removed in favour of concurrent-lane conflict detection (CL-6952)Interface — short xAI 429s report as retryable rate limits instead of quota exhaustion (CL-6935)
Internal —
--efforton the eval runner plus the--configOAuth fix (CL-6973) · outcome records tagged with the serving model so rates have a denominator (CL-6968) · tool-name classification unified, auto-allow membership unchanged and pinned (CL-6809) · director prompt hygiene (CL-6807) ·report.requiredSectionsdeleted (CL-6969)Also fixes a mistake of mine: #551's changelog entry had landed inside the already-released 0.2.106 section because of how I resolved its conflict. Moved to 0.2.107 and rewritten to match the section's voice.
No known-issues section, per the release rules.