Repository navigation
chore(deps): update fro-bot/agent to v0.130.0 - #744
Merged
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.129.0→v0.130.0Release Notes
fro-bot/agent
v0.130.0Compare Source
What's new
OpenCode V2 support is now ready across the workspace and gateway, while the default image remains on V1 until it is explicitly built with the pinned V2 version. The workspace reports its OpenCode version through readiness, allowing the gateway to select the matching run loop without a separate gateway configuration change; deploy the gateway and workspace together when switching. V2 sessions start with a fresh database, and the workspace smoke test now exercises the pinned V2 image, plugins, and readiness path. #1977, #1980, #1979, #1983, #1985, #1988
V2 runs can restore existing V1 session data during the transition, then save to generation-specific V2 S3 and Actions cache keys. Restore checks prefer V2 data and fall back through the existing V1 stores, keeping the two generations' keys isolated. The gateway's V2 run loop also tracks child sessions and background shells and waits for the workspace directory to become quiet before releasing it; if that cannot be confirmed, it quarantines the run. #1981, #1985
Full changelog
0.130.0 (2026-10-30)
Features
Build System
Bug Fixes
Code Refactoring
Miscellaneous Chores
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.