chore(main): release 1.3.0

[github-actions]

🤖 I have created a release beep boop

1.3.0 (2026-07-06)

Features

• config: support plugin tuple options (f8be232)

---

This PR was generated with Release Please. See documentation.

[DanilAgafonov]

@dialupdisaster, is that possible to release it? I really would love to use ability to configure it not via env vars, but rather by opencode.json.

[github-actions]

🤖 Created releases:

• v1.3.0

🌻

[DanilAgafonov]

Thank you @dialupdisaster for merging and cutting 1.3.0 — much appreciated, I've been looking forward to configuring this via opencode.json instead of env vars! 🙏

One heads-up: the "Publish to npm" job failed, so 1.3.0 made it to a GitHub release but isn't on npm yet (npm view @devtheops/opencode-plugin-otel version still returns 1.2.2). The failure is an EBADENGINE mismatch in the release workflow:

npm error code EBADENGINE
npm error engine Not compatible with your version of node/npm: npm@12.0.1
npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error notsup Actual:   {"npm":"10.9.2","node":"v22.14.0"}

The job pulls npm@12.0.1, which needs Node ≥ 22.22.2, but the runner is on Node 22.14.0. Bumping the workflow's Node (e.g. actions/setup-node to a current 22.22+/24 LTS) — or pinning a Node-22.14-compatible npm — should let the publish through. Would you be able to re-run the publish once that's sorted? Thanks again!

[dialupdisaster]

thanks for the heads up @DanilAgafonov, it should be fixed now.