Skip to content

Revert Hono deletion and cleanup follow-up (temporary, fixes #26546)#26548

Closed
kitlangton wants to merge 1 commit into
devfrom
kit/restore-hono-temporary
Closed

Revert Hono deletion and cleanup follow-up (temporary, fixes #26546)#26548
kitlangton wants to merge 1 commit into
devfrom
kit/restore-hono-temporary

Conversation

@kitlangton
Copy link
Copy Markdown
Contributor

Summary

Reverts the Hono backend deletion (#25667) and its cleanup follow-up (#26542).

v1.14.42 (released after #25667) broke startup for users with plugins that depend on the Hono wire format — most visibly `opencode-gemini-auth`, see #26546. The plugin's `auth.set` call surfaces a 400 from the HTTP API, the SDK throws, the error bubbles to the top-level catch in `index.ts`, and the response body lands on stdout instead of the TUI starting.

Restoring Hono as the default backend on stable channels while we investigate the actual plugin compatibility story. The HTTP API code added between #25667 and now (compression middleware, cors-vary fix, fence layer, lifecycle log, account error mapping, validation error response shape, etc.) is preserved — those still apply on the HTTP API path for users on `dev`/`beta` channels (`OPENCODE_EXPERIMENTAL_HTTPAPI` defaults on for those).

Conflict resolution

7 conflicts in test files + `control-plane/types.ts`. All resolved by taking the pre-deletion side (where Hono code lives), since the goal is to restore the prior state. Post-deletion follow-up PRs that re-touched these files have minor formatting overlaps; the substance of those PRs (test expansions, etc.) remains in adjacent files.

After this lands

  • v1.14.43 auto-publishes from `dev` push and ships the revert
  • arjun + others on stable get Hono back, plugin compat restored
  • We can investigate gemini-auth + design the actual HTTP API plugin compat story (matching Hono's exact validation error wire format, or a versioned migration) without a blocked release

Test plan

  • CI green
  • Manual: `opencode` (no args) launches TUI on stable build

…eanup

This reverts:
- 28b0359 research: delete Hono backend (do not merge) (#25667)
- b24a4e8 chore(server): clean up post-Hono-deletion scar tissue (#26542)

v1.14.42 broke startup for users with plugins that depend on the
Hono wire format (most visibly opencode-gemini-auth, see #26546).
Restoring Hono as the default backend on stable channels while we
investigate the actual plugin compatibility story.

OPENCODE_EXPERIMENTAL_HTTPAPI flag and dual-backend selection come
back. Stable installs default to Hono; dev/beta default to HTTP API.

Conflict resolution: took the pre-deletion side for control-plane
schemas and the seven test files where post-deletion follow-up PRs
had also touched the conflicting lines. The HTTP API code added
since the deletion (compression, cors-vary, fence, lifecycle log,
account error mapping, etc.) is preserved as-is — those still apply
on the HTTP API path for users on dev/beta channels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant