Skip to content

ci(opencode): bump pinned OpenCode to v1.19.3 - #598

Merged
ualtinok merged 4 commits into
mainfrom
ci/bump-opencode-1.19.3
Oct 19, 2026
Merged

ualtinok merged 4 commits into
mainfrom
ci/bump-opencode-1.19.3

Conversation

@cortexkit-public-bot

@cortexkit-public-bot cortexkit-public-bot Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Automated bump of .github/opencode-version.txt from 1.18.30 to 1.19.3.

Upstream release notes: https://github.com/anomalyco/opencode/releases/tag/v1.19.3

What this changes

All three E2E harnesses now install OpenCode v1.19.3:

  • tests/docker/Dockerfile.linux-x64 (Linux Docker E2E)
  • tests/macos-e2e/run.sh (macOS native E2E)
  • tests/windows-e2e/run.ps1 (Windows native E2E)

Merge gate

The Tests workflow on this PR exercises the new version against the
full E2E matrix. If any platform regresses, do not merge — file
an upstream issue or hold the bump until upstream fixes the
regression. Pin will stay at 1.18.30 until this PR is merged.

Tests runs automatically because this PR was opened with a PAT.
yes


Summary by cubic

Bumps the pinned OpenCode version from 1.18.30 to 1.19.3 so the Linux Docker, macOS native, and Windows native E2E harnesses exercise the new release in this PR's CI run. Do not merge if any platform fails — the pin stays at 1.18.30 until this lands.

  • The bump workflow now recaptures the OpenCode 1 parity contracts with capture-host1-contracts.mjs, so changed host behavior ships with the bump instead of failing the merge queue.
  • The capture reads aimock request snapshots on demand and waits for a newer one, fixing a race where stale or half-written request files produced wrong wire-path observations.
  • Captured provider-config and edit-family observations for 1.19.3 replace the 1.18.30 transcripts; the capture refuses to update fixtures when previously rejected provider shapes start working or the edit-family fragments change.
  • The load-matrix test reads the pinned version from .github/opencode-version.txt instead of matching the 1.18. pattern.
  • The bump workflow now also generates a slice descriptor for the raised PR.

Written for commit 580936f. Summary will update on new commits.

View guided diff Turn on auto-fix

RetriggerView in GreptileConfidence Score: 5/5

The reviewed changes appear safe to merge once the required CI checks pass.

Summary

Bumps OpenCode from 1.18.30 to 1.19.3 and updates the captured host contracts.

  • The E2E pin and plugin version check now move together.
  • Each OpenCode bump now carries matching V1 parity evidence.

Both earlier, unnumbered findings are addressed. No new actionable issue was found. Tests were not run.

Reviews (4) · Last reviewed commit: "Read aimock request snapshots on demand ..." · Reviewed by Greptile

Auto-generated by .github/workflows/bump-opencode.yml.

Bumps .github/opencode-version.txt from 1.18.30 -> 1.19.3.
All three E2E harnesses (Linux Docker, macOS native, Windows native)
read this file, so PR-time CI exercises the new OpenCode version on
every supported platform before merge. If any platform regresses,
the PR will fail and you'll know immediately.
Comment thread .github/opencode-version.txt
Co-authored-by: alfonso-aft <289616620+alfonso-aft@users.noreply.github.com>
@ualtinok
ualtinok added this pull request to the merge queue Oct 19, 2026
@ualtinok
ualtinok removed this pull request from the merge queue due to a manual request Oct 19, 2026
Co-authored-by: alfonso-aft <289616620+alfonso-aft@users.noreply.github.com>
Comment thread tests/docker/opencode2/contract/capture-host1-contracts.mjs Outdated
The mock wrote its request list every 100 ms, so a read right after OpenCode
exited could see an old or half-written file, and invalid JSON counted as zero
requests. The capture now asks for a numbered snapshot, waits for it, and
treats a malformed snapshot as an error.

Co-authored-by: alfonso-aft <289616620+alfonso-aft@users.noreply.github.com>
@ualtinok
ualtinok enabled auto-merge October 19, 2026 16:08
@ualtinok
ualtinok disabled auto-merge October 19, 2026 16:09
@ualtinok
ualtinok added this pull request to the merge queue Oct 19, 2026
Merged via the queue into main with commit 13a69e2 Oct 19, 2026
49 of 50 checks passed
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