chore(deps): update fro-bot/agent to v0.102.0 - #372
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.101.0→v0.102.0Release Notes
fro-bot/agent (fro-bot/agent)
v0.102.0Compare Source
What's new
The action's output-mode resolution is now fully explicit — the temporary backward-compatibility detector introduced in v0.100.0 has been removed after one full minor version observed no regressions.
The legacy phrase-matching logic (
legacyWouldSelectBranchPr) and itscore.warningare gone from the execute phase.resolveOutputModeno longer accepts apromptparameter, which was already unused since #1400 made delivery mode authoritative — removing it makes the function signature honest.autocontinues to resolve deterministically toworking-dir, and explicitbranch-prremains the only way to opt into branch/PR delivery.The
output-mode-migrationstep output drops itslegacyWouldSelectBranchPrfield, which could only ever have reportedfalseafter the detector was zeroed out. It now surfacesrequestedandresolvedonly. #1443The default OpenCode build advances to
1.18.18+harness.39b7b193. Both the action default (DEFAULT_OPENCODE_VERSIONinconstants.ts) and the workspace Dockerfile (ARG OPENCODE_VERSION) are pinned to the same build, ensuring the action entrypoint and the workspace executor run identical patched OpenCode. #1440Full changelog
0.102.0 (2026-08-21)
Features
Build System
Bug Fixes
Documentation
Continuous Integration
Code Refactoring
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.