Skip to content

chore: release v0.8.3 - SDK 1.4.7 compatibility#88

Merged
tryweb merged 4 commits intomainfrom
release/v0.8.3
Apr 17, 2026
Merged

chore: release v0.8.3 - SDK 1.4.7 compatibility#88
tryweb merged 4 commits intomainfrom
release/v0.8.3

Conversation

@tryweb
Copy link
Copy Markdown
Owner

@tryweb tryweb commented Apr 17, 2026

Release v0.8.3

Summary

SDK 1.4.7 compatibility update with test mock fix and documentation.

Changes

  • @opencode-ai/sdk and plugin upgrade:

    • Upgrade @opencode-ai/plugin: 1.4.3 → 1.4.7
    • Upgrade @opencode-ai/sdk: 1.4.3 → 1.4.7
  • Test mock compatibility fix:

    • Updated ToolContext.ask() mock to use Effect.void instead of Promise
    • Added bun installation to Dockerfile for test execution
  • Documentation:

    • Added docs/OPENCODE_COMPATIBILITY.md with SDK version history
    • Documented SDK 1.4.4-1.4.7 breaking change (Effect type)

Verification

  • Local release:check passed
  • TypeScript typecheck: passed
  • Build: passed
  • Tests: 199 pass, 1 skip, 1 fail (pre-existing)
  • E2E tests: all pass

Files Changed

  • package.json (version bump)
  • CHANGELOG.md
  • README.md / README_zh.md
  • Dockerfile (add bun)
  • Dockerfile.opencode (update OpenCode to 1.4.7)
  • test/regression/plugin.test.ts (Effect.void mock)
  • docs/OPENCODE_COMPATIBILITY.md

Developer added 4 commits April 17, 2026 18:39
- Upgrade @opencode-ai/plugin: 1.4.3 → 1.4.7
- Upgrade @opencode-ai/sdk: 1.4.3 → 1.4.7
- Fix test mock to use Effect.void for SDK 1.4.7 compatibility
- Add bun to Dockerfile for test execution
- Update OpenCode version to 1.4.7
- Add SDK 1.4.4-1.4.7 compatibility documentation
- Change test scripts to use node --test instead of bun test
- Bun has issues with nested test() calls
- Add timeout to latency benchmark test (30000ms)
- Fix test() signature: use (name, options, fn) format instead of (options, fn) with name property
- Simplify verify script to use npm run test for proper glob expansion
- This fixes CI failure on Node 20 verify-matrix job
…egular tests

- Latency benchmark should only run via npm run benchmark:latency
- Exclude from verify/test scripts to prevent CI timeout
- The benchmark test takes too long for regular CI verification
@tryweb tryweb merged commit b902a0a into main Apr 17, 2026
9 checks passed
@tryweb tryweb deleted the release/v0.8.3 branch April 17, 2026 10:53
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