⬆️ bump @opentelemetry/exporter-* devDeps to ^0.218.0

[jimmyhoran]

Summary

Follow-up to the runtime-dep bump PR (which targets the same 0.200.0 → 0.218.0 move for sdk-node + instrumentation). This one bumps the OTel exporter devDeps so the test/example surface stays on the same OTel line as the runtime deps:

 "devDependencies": {
     ...
-    "@opentelemetry/exporter-metrics-otlp-proto": "^0.200.0",
-    "@opentelemetry/exporter-trace-otlp-http": "^0.200.0",
-    "@opentelemetry/exporter-trace-otlp-proto": "^0.200.0",
+    "@opentelemetry/exporter-metrics-otlp-proto": "^0.218.0",
+    "@opentelemetry/exporter-trace-otlp-http": "^0.218.0",
+    "@opentelemetry/exporter-trace-otlp-proto": "^0.218.0",
     ...
 }

Why

devDeps only — no consumer impact. Without this, the test suite and examples are exercising a different OTel exporter line (0.200.x) from the runtime deps (0.218.x post the parent PR). Keeping them aligned makes test results representative of what consumers will see.

Sequencing

Branched on top of bump-otel-sdk-node-to-0.218. Best to merge after the parent PR lands; this one rebases cleanly onto main once that's done.

Verification

• bun run build succeeds (CJS + ESM).
• bun test --preload ./test/test-setup.ts: 61 pass / 1 fail, same single pre-existing @elysiajs/eden import failure that's already on main. No new regressions.

The 2.x stable devDeps (context-async-hooks, exporter-jaeger, sdk-metrics, sdk-trace-node, sdk-trace-web) are left at their current ^2.0.0 ranges — they're on a wide enough caret to converge naturally with whatever sdk-node@0.218.0 pulls in transitively.

[coderabbitai]

Warning

Rate limit exceeded

@jimmyhoran has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 49 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 73d3bc09-30bf-4d53-9f43-382a0da5635c

📥 Commits

Reviewing files that changed from the base of the PR and between b85a5f5 and d2c8c38.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jimmyhoran]

Consolidating into #81 — one PR for the full @opentelemetry/* ^0.218.0 alignment is cleaner for review than splitting runtime vs devDeps when both serve the same intent.