Which Sentry SDK versions have Bicho interoperability tests? #60
|
Which SDK versions are covered by Bicho tests, and what does that coverage establish for other languages or framework integrations? |
Replies: 1 comment
|
The current interoperability tests cover That is narrower than a claim that every Sentry SDK works. Another language SDK, framework wrapper, transport, or SDK release can emit different envelope items or require different authentication behavior. The tests do not establish support for every automatic integration or for tracing, replay, profiling, or artifact uploads. For an untested combination, start with a dedicated test project. Keep error capture enabled, remove unsupported integrations, configure the generated Bicho DSN, and supply backend secret headers if required. Capture a known exception, await the SDK's delivery mechanism, and read the stored event through MCP or the API. Check its stack and metadata, not just the HTTP status. Include the exact SDK version and a sanitized transport response when reporting an interoperability problem. Documentation - Move from Sentry Source - Bicho: Sentry SDK interoperability tests Source - Bicho: Sentry runtime tests |
The current interoperability tests cover
@sentry/node11.8.0 and@sentry/browser11.8.0. The Node suite exercises SDK serialization and actual HTTP delivery with the Node and fetch transports. It reads stored evidence back and resends the same envelope to check project-scoped deduplication. A Workers-runtime suite also exercises browser-client delivery inside workerd.That is narrower than a claim that every Sentry SDK works. Another language SDK, framework wrapper, transport, or SDK release can emit different envelope items or require different authentication behavior. The tests do not establish support for every automatic integration or for tracing, replay, profiling, or artifact uploads.