This branch (otel-v1-main) contains a version of the OpenLLMetry JS SDK that is compatible with OpenTelemetry JavaScript SDK v1.30.1 and earlier versions.
- @opentelemetry/api:
^1.7.0(downgraded from^1.9.0) - @opentelemetry/core:
^1.30.1(downgraded from^2.0.1) - @opentelemetry/resources:
^1.30.1(downgraded from^2.0.0) - @opentelemetry/sdk-trace-base:
^1.30.1(downgraded from^2.0.0) - @opentelemetry/instrumentation:
^0.48.0(downgraded from^0.203.0) - @opentelemetry/sdk-node:
^0.48.0(downgraded from^0.203.0)
- TypeScript Interface Updates: Fixed
InstrumentationModuleDefinition<T>generic type parameters across all instrumentation packages - SDK Configuration: Updated
NodeSDKconfiguration to usespanProcessor(singular) instead ofspanProcessors(plural) as required by v1.x - API Version Compatibility: Ensured all packages use compatible API versions
The branch has its own GitHub Actions workflow (.github/workflows/release-otel-v1.yml) that:
- Triggers on pushes to
otel-v1-mainbranch - Automatically adds
-otel-v1suffix to version numbers - Publishes to npm with
otel-v1dist-tag - Creates GitHub releases with appropriate tagging
- Main branch releases:
0.16.2,0.17.0, etc. - OTel v1 branch releases:
0.16.2-otel-v1,0.17.0-otel-v1, etc.
For users on OpenTelemetry v2.x (latest):
npm install @traceloop/node-server-sdkFor users on OpenTelemetry v1.x:
npm install @traceloop/node-server-sdk@otel-v1To keep this branch up-to-date with the main branch:
-
Merge main branch changes:
git checkout otel-v1-main git merge main
-
Resolve any conflicts related to OpenTelemetry dependencies
-
Test the build to ensure v1 compatibility is maintained
-
Push changes to trigger automated release
Before releasing, ensure:
- All instrumentation packages build successfully
- The main SDK package compiles (may have some remaining type issues with complex scenarios)
- Basic functionality works with OpenTelemetry v1.x setups
-
Type Compatibility Errors: The v1.x OpenTelemetry packages have different TypeScript interfaces. Most have been fixed, but complex scenarios may still have issues.
-
Peer Dependency Warnings: Some peer dependency warnings are expected due to the version differences between packages.
-
Build Failures: If new features from main use v2.x-only APIs, they'll need to be adapted or conditionally compiled for v1 compatibility.
For issues specific to the OpenTelemetry v1 branch, please:
- Check if the issue exists in the main branch
- Verify OpenTelemetry version compatibility
- Open issues with
[otel-v1]prefix in the title