Repository navigation
Conversation
|
🟢 Contributor eligibility requirements met for @felipecrs.
|
felipecrs
force-pushed
the
feat/opencode-1-19-support
branch
from
October 23, 2026 23:28
0ea8d72 to
b5a49b4
Compare
felipecrs
marked this pull request as ready for review
October 23, 2026 23:32
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.
Fixes #22
Problem
OpenCode 1.x is still maintained: 1.19.4 is the newest release on npm. The version gates only accepted the exact 1.17.20 pin or a validated 2.0.x release, so any transfer touching a 1.19.x CLI failed with:
Resulting behavior
Any 1.19+ 1.x release is now accepted, since the public export, import, and session-list shapes are unchanged within the family, alongside the existing validated 2.0.x. The pinned integration target moves from 1.17.20 to 1.19.4, so writer metadata, the unvalidated-version baseline, and the CI-installed binary follow the newest 1.x release. Releases other than the exact pin still emit the existing
unvalidated_source_version/unvalidated_target_versionwarnings.One decision to confirm: raising the floor means 1.17.20 and 1.18.x are now rejected. I kept a floor rather than a wider window because the corpus and native evidence are validated against one pinned binary per major line. If you'd rather keep 1.17.20 accepted as well, say so and I'll rebase.
How I tested it
uv run ruff check .anduv run ruff format --check src tests scripts .github/scripts .github/testspython3 -m unittest discover .github/testsuv run pytest -q: 1749 passed, 61 skippedsmigrate transfer --dry-runon a real 1.19.4 OpenCode session: 18 portable records, clean exit, and no version mismatchtest_version_schema_gate: 1.19.0 and 1.19.4 accepted, 1.17.20, 1.18.9 and 1.0.0 rejected, 2.0.x unchangedNotes
/Library/Application Support/opencodeenabled_providerswhitelist cannot be redirected with environment variables and can hide the synthetic test provider. The loopback tests probe for this and skip when it happens.