chore(release): pending release v0.52.0#743
Merged
Merged
Conversation
The 1.14.42+ /event SSE SyncEvent regression that forced the 1.14.41 pin (message.part.updated/message.updated/session.next.* not reaching bus.subscribeAll subscribers) is fixed upstream in 1.15.13. Verified against an isolated 1.15.13 server: the harness renders tool-call output and assistant text end-to-end through the existing message.part.updated handler. 1.15.13 shifts the event contract — the tool lifecycle and text now arrive via message.part.updated / message.part.delta, and session.next.tool.* / session.next.text.delta no longer fire. The existing streaming.ts handlers already cover the new contract; legacy session.next.* handlers are retained as fallback. Renovate caps at <=1.15.13 so further bumps stay deliberate. Scope is the action + runtime client bump (DEFAULT_OPENCODE_VERSION, @opencode-ai/sdk root + runtime). The workspace executor image stays on 1.14.41 until the gateway mention-loop tool-progress renderer migrates to the new contract; a Renovate rule holds the workspace Dockerfile ARG at 1.14.41 so the global cap cannot bump it ahead of that cutover.
marcusrbrown
approved these changes
Jun 3, 2026
…744) * feat(gateway): render tool progress on the OpenCode 1.15.13 event contract The mention-loop renderer in run-core.ts surfaced Discord tool-progress lines only from session.next.tool.called/success, which no longer fire on OpenCode 1.15.13. Add a message.part.updated handler (partType:'tool', state.status:'completed') that renders the same progress line, mirroring the action-tier streaming handler. Text continues to stream via message.part.delta; the legacy session.next.tool.* handlers are retained as an inert fallback. * build(workspace): bump baked OpenCode to 1.15.13 The gateway mention-loop renderer now handles the 1.15.13 event contract, so the workspace executor image can move off the deliberate 1.14.41 hold. Bumps deploy/workspace.Dockerfile ARG OPENCODE_VERSION 1.14.41 → 1.15.13 and removes the file-scoped Renovate rule that pinned it below the global cap; the workspace ARG now tracks DEFAULT_OPENCODE_VERSION under the <=1.15.13 cap.
fro-bot
Bot
changed the title
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.
Pending Release: v0.52.0
This PR tracks changes pending release. Released on the next auto-release cycle (Sunday/Wednesday) or via manual dispatch.
Merge this PR to trigger a release. Releases also run automatically on Sunday/Wednesday at 20:00 UTC, or via manual workflow dispatch.
Commits Since Last Release
Auto-generated by the release pipeline. Updated: 2026-06-03 15:36 UTC