Repository navigation
chore(deps): update fro-bot/agent to v0.130.3 - #4069
Open
fro-bot[bot] wants to merge 1 commit into
Open
fro-bot[bot] wants to merge 1 commit into
fro-bot[bot] wants to merge 1 commit into
Conversation
fro-bot
Bot
added
automerge
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
2 times, most recently
from
October 27, 2026 20:55
ecb738a to
7e517fc
Compare
fro-bot
Bot
changed the title
This was referenced Oct 28, 2026
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
from
October 28, 2026 06:11
7e517fc to
0f7f7d7
Compare
fro-bot
Bot
changed the title
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
from
October 29, 2026 06:21
0f7f7d7 to
1c29a37
Compare
fro-bot
Bot
changed the title
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
from
October 30, 2026 15:18
1c29a37 to
5722a49
Compare
fro-bot
Bot
changed the title
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
from
October 31, 2026 04:57
5722a49 to
12e4d14
Compare
fro-bot
Bot
changed the title
fro-bot
Bot
force-pushed
the
renovate/github-actions
branch
from
October 31, 2026 05:02
12e4d14 to
750d09f
Compare
fro-bot
Bot
changed the title
This branch has not been deployed
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.125.1→v0.130.3Release Notes
fro-bot/agent
v0.130.3Compare Source
Build System
v0.130.2Compare Source
What's new
OpenCode V2 pin updates from Renovate now regenerate their SHA-256 digests automatically, preventing builds from failing because the version changed while the old digests remained. The pin’s Renovate rule runs the sync script before rebuilding the Action bundle, so the embedded pin is refreshed in the same update.
This removes the previous manual regeneration step; the configured commands also match the Renovate action’s allowed-command rules. #1998
Full changelog
0.130.2 (2026-10-31)
Build System
Bug Fixes
v0.130.1Compare Source
What's new
OpenCode V2 workspace agents could start successfully but fail their first model request with a 401 because fresh per-spawn databases skip the migration that imports provider credentials. Each spawn now provisions credentials from the protected workspace secret and checks that the configured model's provider has a usable credential before readiness; missing credentials keep the spawn unready. The gateway proxy also limits forwarding to the exact routes its client needs, preventing access to upstream credential-management endpoints, and the workspace smoke test now verifies an actual model request and the no-credential failure path. #1993
Release jobs were spending several minutes rerunning install, lint, and build checks when semantic-release pushed its release commit and tag, even though CI had already run them. The release job now skips installing git hooks, avoiding those redundant pre-push checks while leaving the release-notes narration watch intact. #1991
Full changelog
0.130.1 (2026-10-31)
Bug Fixes
Continuous Integration
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
v0.129.0Compare Source
What's new
Stock OpenCode V2 binaries can now be installed with integrity checks against both a repository-recorded digest and the release’s
SHA256SUMS. The pin currently records V2.2.0; the workspace image verifies its musl asset too, while the default remains on the existing V1 harness path. #1973Full changelog
0.129.0 (2026-10-28)
Features
Bug Fixes
Code Refactoring
v0.128.0Compare Source
What's new
Workflows that still pass the five
enable-omo,enable-omo-slim,omo-version,omo-providersoromo-slim-presetinputs will now get GitHub’s “Unexpected input” annotation and continue using the default configuration. The Action no longer installs oMo or oMo Slim, their agents, or provider routing; use thebuildagent, bundled Systematic plugin, andagent,model,auth-jsonandopencode-configinputs instead. Provider configuration must now be set throughauth-jsonandopencode-config. #1968The removal also eliminates the oMo-specific Bun installation path and plugin/configuration guards. The tools cache now uses a v2 key, so each runner will incur one cold cache miss after upgrading; the default generated config remains unchanged. #1968
Full changelog
0.128.0 (2026-10-28)
⚠ BREAKING CHANGES
Features
Continuous Integration
v0.127.0Compare Source
What's new
The Action and workspace image now default to the patched OpenCode 1.19.4 harness. Its 15 local carries were retained and verified against the upstream release, and the harness build, SDK, and Bun versions are aligned; the harness also accounts for upstream changes to update checks and session sharing. #1959 #1962
Runs now wait for OpenCode’s
server.connectedevent before sending a prompt, so permissions, early output, idle state, and errors emitted immediately after the prompt are not lost. If the event stream never connects, the attempt fails before sending the prompt and can retry on a fresh stream; the same connection barrier is used by both the gateway and Action. #1956An early abort on a cold or still-preparing session could previously look stopped before the prompt had actually started, releasing the session for another run. The gateway now requires a terminal reply to the latest user turn as positive stop evidence, re-aborts while a root remains live, and quarantines sessions when that evidence is missing; runs that never sent a prompt keep the fast path. #1965
CI now selects Bun from the root
packageManagerfield and checks that the installed version matches it, replacing duplicated workflow version literals that had left jobs on an older Bun during harness verification. #1963Full changelog
0.127.0 (2026-10-27)
Features
Build System
Bug Fixes
Documentation
Continuous Integration
v0.126.0Compare Source
What's new
Operators can now see why an active gateway run is still draining, rather than seeing only a generic running state. The live status reports one of four bounded reasons—agent work, a pending reply, background-task completion, or completion confirmation—and refreshes only when the reason changes; approval and question prompts take precedence. The reason is in-memory status only, is omitted from run summaries, and is cleared when the event loop exits. #1954
Gateway run records are now more likely to reach an accurate terminal state when storage writes fail. Terminal writes retry with bounded attempts and re-check record ownership before writing, while failure replies and operator updates proceed without waiting for the write; a periodic sweep reconciles stale executing or acknowledged records during gateway uptime, leaving queued work untouched. #1950
Full changelog
0.126.0 (2026-10-27)
Features
Build System
Bug Fixes
Miscellaneous Chores
v0.125.5Compare Source
What's new
Workspace image builds no longer fail whenever Alpine replaces a pinned package version in its repository: package installs now use the versions available in the pinned Alpine 3.24 base image, while the base image remains pinned by digest. This avoids waiting for a Renovate bump to restore builds after an exact package version disappears; rebuilding the same ref may therefore pick up newer package versions.
Gateway runs now terminate when OpenCode’s event stream disconnects or stops producing events, instead of remaining stuck as running. Transport errors are surfaced, a 30-second silence watchdog counts heartbeats as activity, and the event connection closes on run exit. Pending approvals and questions are rejected when termination begins, before the existing abort-and-confirm barrier completes. #1946 #1947
Full changelog
0.125.5 (2026-10-26)
Build System
Bug Fixes
Documentation
Miscellaneous Chores
v0.125.4Compare Source
Build System
Bug Fixes
Code Refactoring
Miscellaneous Chores
v0.125.3Compare Source
What's new
The Action no longer writes reasoning-part deltas into its response-text log, and gateway runs now treat an owned child session’s terminal error as an unknown child outcome rather than failing the whole run. Root-session errors still fail as before, and the gateway continues to learn child outcomes from task-completion notices. #1912
Gateway ownership reconciliation now has a 15-second bound on both periodic passes and the root-idle pass, so a stalled status request cannot prevent later reconciliation for the rest of a run. Late results are ignored after timeout or teardown, and early run failures now dispose of the reconciler interval. #1907
When a gateway run encounters a dirty shared checkout, it can now preserve the old checkout as a backup, install a fresh default-branch clone, and retry the update automatically. Recovery proceeds only while the run holds the repository lock, enough time remains for the bounded recovery steps, and the workspace confirms it is quiescent; the preserved backups remain subject to the existing retention cap. #1918
GitHub App installation-token requests in the gateway now have a shared 30-second deadline across installation discovery and token minting, preventing stalled requests from holding a repository lock or concurrency slot indefinitely. A late token result cannot trigger a workspace request after the bound, and timeout diagnostics avoid logging error messages or tokens. #1919
Gateway and workspace-agent logs now identify checkout refusals and failures with run IDs, and record forwarded workspace teardown responses with their status and duration. The new log fields omit checkout paths, request bodies, headers, and workspace paths. #1915
Full changelog
0.125.3 (2026-10-23)
Build System
Bug Fixes
Documentation
v0.125.2Compare Source
What's new
Early stops now wait for owned work to become quiescent before releasing coordination state. The gateway aborts its root session and quarantines a run if it cannot confirm the session has stopped, while Action drain reconciliations and child aborts are bounded;
timeout: 0now allows observed background work to finish without a drain deadline. The Action and gateway also share a lease-renewal loop, with bounded ticks, cancellation, and ownership-checked ETag recovery when a renewal's result is lost, preventing stale lease state from blocking later renewals or release. #1899, #1902, #1906The bundled Node.js runtime and Docker images now use v24.22.1, a security release that includes fixes across HTTP, DNS, TLS, permissions, and cryptography. The mitmproxy image advances to v12.3.0, which removes eMudhra CAs from the trust list in precompiled binaries and includes fixes to proxy protocol handling and mitmweb. #1896, #1903
Full changelog
0.125.2 (2026-10-22)
Build System
Bug Fixes
Continuous Integration
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.