chore(release): pending release v0.99.0 - #1394
Merged
Merged
Conversation
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com>
* fix(harness): move base to OpenCode 1.18.18 Sessions with history older than 2026-08-14 silently stopped responding. OpenCode message IDs pack a timestamp into a 48-bit field, so the value wraps every 795 days; the most recent wrap was 2026-08-14T11:19:55Z. After it, new IDs sort below every earlier one, which made the agent loop's exit guard permanently true — prompts were accepted and never sent to the model, with no error surfaced. Upstream fixed the ordering in anomalyco/opencode#40990 and #40991, merged two days after the 1.18.14 tag we were pinned to. Moving the base to 1.18.18 picks both up; no new integration refs are needed, and no session data has to be migrated. All twelve carried refs remain open or unmerged upstream, so the carry set is unchanged. DEFAULT_OPENCODE_VERSION stays put — sync-default-version moves it once a release produces a real integration SHA. The underlying truncation is still present upstream, so the wrap recurs around 2028-10-17. * chore: re-pin dependency source clones to OpenCode 1.18.18 The read-only clones under .slim/clonedeps/repos/ track the harness base_version so a source check reflects what we actually ship. They were still at 1.18.14 after the base moved. This staleness had teeth: a search of the 1.18.14 tree for the message-ID ordering bug found nothing and looked like evidence the bug was unreported, when upstream had already fixed it in 1.18.18. The re-pinned tree now shows the isAfter() helper in session/message-v2.ts and the structural parent guard in session/prompt.ts, with the old lexical comparison gone.
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com>
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com> Co-authored-by: Fro Bot <80104189+fro-bot@users.noreply.github.com>
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com>
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.
Pending Release: v0.99.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-08-15 00:26 UTC