Skip to content

chore(release): pending release v0.99.0 - #1394

Merged
marcusrbrown merged 6 commits into
releasefrom
next
Aug 15, 2026
Merged

chore(release): pending release v0.99.0#1394
marcusrbrown merged 6 commits into
releasefrom
next

Conversation

@fro-bot

@fro-bot fro-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

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

fro-bot Bot and others added 2 commits August 13, 2026 16:42
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.
@fro-bot
fro-bot Bot requested review from fro-bot and marcusrbrown as code owners August 14, 2026 23:27
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com>
@fro-bot fro-bot Bot changed the title chore(release): pending release v0.98.6 chore(release): pending release v0.99.0 Aug 15, 2026
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>
fro-bot Bot added 2 commits August 15, 2026 00:23
Co-authored-by: fro-bot[bot] <109017866+fro-bot[bot]@users.noreply.github.com>
@marcusrbrown
marcusrbrown merged commit 028f85b into release Aug 15, 2026
1 check passed
@marcusrbrown
marcusrbrown deleted the next branch August 15, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant