chore(deps): update fro-bot/agent to v0.107.0 - #889
Merged
Conversation
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 contains the following updates:
v0.106.2→v0.107.0Release Notes
fro-bot/agent (fro-bot/agent)
v0.107.0Compare Source
What's new
Authorized mentions on a PR can now submit PR reviews — approve, request changes, or re-review — rather than being limited to posting a comment. Previously, when a
@fro-botmention triggered a run on a PR, the agent could reach a review conclusion but the response validator would reject it:"verdict" is only valid for surface "pr-review", got "pr-comment". The turn was consumed, nothing was posted, and on repos where branch protection required Fro Bot's approval there was no in-band way to move aCHANGES_REQUESTEDreview back toAPPROVED.The fix introduces a
pr-review-permittedsurface distinct from the required-verdictpr-reviewsurface used forpull_requesttriggers. A mention on a PR routes to this surface: if the agent produces a verdict the run submits a review; if it produces only prose the run posts a comment. The existing authorization gate — which already restricts mention runs to non-botOWNER/MEMBER/COLLABORATORauthors — is unchanged, so no new permission machinery was added. The fork/selfAPPROVEguard and the head-SHA re-check are inherited by mention-initiated reviews.As a structural hardening, every response-surface consumer now indexes a shared
RESPONSE_SURFACE_POLICIEStable checked with asatisfies Record<ResponseSurface, …>constraint, so an unhandled surface fails compilation rather than silently falling through to comment delivery. Additionally, a stray verdict on a comment-only surface now degrades gracefully — the frontmatter is dropped and the prose is posted with a warning — rather than discarding the entire agent turn. A newdelivery-kindaction output (review/comment/none) lets callers observe which path a run actually took. #1507Full changelog
0.107.0 (2026-08-31)
Features
Documentation
Configuration
📅 Schedule: (in timezone America/Phoenix)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.