npm latest (0.1.0, 2026-06-18) predates every merged fix — please cut a release #18

Summary

The latest version on npm (0.1.0, published 2026-06-18T08:48Z) predates every fix merged into main since then. Because OpenCode resolves plugins from npm, everyone installing @langfuse/opencode-observability-plugin@latest today gets a build that is ~7 weeks old and missing at least 8 merged PRs — including fixes for bugs that are still being re-reported here.

There are no git tags and no GitHub releases, and package.json on main is still 0.1.0, so a bare npm publish would also fail without a version bump.

How I ran into this

Traces in the Langfuse UI show Input but an empty Output column; the assistant text is only visible after drilling into the opencode.generation observation. That is exactly #1.

But this specific half of #1 was already fixed by #2 ("fix(langfuse): capture turn output", merged 2026-06-30), which sets langfuse.observation.output on the root opencode.turn span:

https://github.com/langfuse/opencode-observability-plugin/blob/main/src/langfuse.ts#L574-L580

The fix is simply not in the artifact users install. Verified against the installed tarball at ~/.cache/opencode/packages/@langfuse/opencode-observability-plugin@latest/:

$ npm view @langfuse/opencode-observability-plugin dist-tags time versions
dist-tags = { latest: '0.1.0' }
time = { '0.1.0': '2026-06-18T08:48:44.816Z' }
versions = '0.1.0'

# installed dist/ vs. main:
$ grep -c getTurnObservation dist/langfuse.js   # PR #2, turn-level output
0
$ grep -c compaction dist/langfuse.js           # PR #5
0
$ grep -o 'LANGFUSE_BASE_*URL' dist/index.js    # PR #12
LANGFUSE_BASEURL                                # old spelling only

That last one also means the documented LANGFUSE_BASE_URL env var (#11 / #12) silently does nothing for anyone on npm latest — likely a contributor to #6 and #7 style "no traces appear" reports.

Merged work not published

Request

1. Bump the version on main and publish (e.g. 0.2.0), so @latest reflects merged fixes.
2. Consider a release workflow + git tags so main and npm can't drift this far again — with @latest this stale, issue reports here are effectively describing a June build, which makes triage confusing for everyone (see Traces show input but no output; generations show output but no input #1, where the trace-output half was already fixed on main at the time of reporting).

Environment

• OpenCode plugin entry: "@langfuse/opencode-observability-plugin@latest"
• Resolved to: 0.1.0 (2026-06-18)
• Langfuse: v3.222.0, self-hosted
• macOS (Darwin 25.5.0)