Repository navigation
build: bump OpenCode compatibility baseline to 2.0.22 - #3
Merged
Merged
Conversation
Raise the OpenTUI development ranges to 0.5.14 to satisfy @opencode/plugin 2.0.22's peer requirements. Keep the package version and minimum supported host unchanged.
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.
Update the exact @opencode/plugin and @opencode/theme development pins to 2.0.22 following the completed compatibility review. OpenTUI development ranges move to ^0.5.14 because the new plugin package requires that peer minimum. No plugin source changes, package version bump, or change to the minimum supported OpenCode version (2.0.11).
Validation passed locally: clean npm ci, compatibility check, lint, typecheck, tests, build, and production dependency audit. All GitHub CI and CodeQL checks passed, including the packed-artifact runtime check.