New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: prepare release API 1.9.0/Core 1.25.0/Experimental 0.52.0 #4677
base: main
Are you sure you want to change the base?
chore: prepare release API 1.9.0/Core 1.25.0/Experimental 0.52.0 #4677
Conversation
7d5305c
to
715ecb2
Compare
I reached out to Datadog about this through @Qard. As the PR currently stands it would break dd-trace which I would like to avoid. I think we should delay this for a short time in order to allow them to respond, but I don't want to delay it forever. |
I've forwarded it to the relevant person internally so hopefully we'll come up with some solution soon... |
Any chance of #4536 enhancement having a published release soon? I realize there's a breaking change with a dd lib but was hoping to have the enhancement in a release sooner than that's resolved? Appreciate everyone's efforts here. |
@Qard @dyladan Any chance the dd-trace blockers don't hold back API 1.9.0 enhancements? Is it possible to have a release for API without waiting on dd-trace resolution? Thank you in advance! |
It's possible but it's not ideal. If we release in the current state we will definitely break dd-trace and it reflects poorly on the project. We're doing our best to work with them. Sorry it's delaying the release but please be patient and we'll have a release soon. |
We're going to move forward with this change next week. It looks to me like dd-trace hasn't done anything yet to address the issue, but we have been very clear for months. @pichlermarc please update this PR and we can get it merged when I get back. |
API 1.9.0
🚀 (Enhancement)
Core 1.25.0
🚀 (Enhancement)
xray
Propagator viaOTEL_PROPAGATORS
environment variable #4602 @anuraags🐛 (Bug Fix)
getEnv()
andgetEnvWithoutDefaults()
when aprocess
polyfill is used #4648 @pichlermarcgetEnvWithoutDefaults()
would useprocess.env
if it was defined when running in a browser, whilegetEnv()
would always use_globalThis
. Now both use_globalThis
when running in a browser.@opentelemetry/resources
Experimental 0.52.0
💥 Breaking Change
@opentelemetry/otlp-transformer
#4542 @pichlermarcconvert()
now returns an empty object and will be removed in a follow-upResponseType
type parameter@opentelemetry/otlp-transformer
#4581 @pichlermarcconvert()
has been removed from all exportersRequestType
has been replaced by aResponseType
type-argumentServiceRequest
has been replaced by aServiceResponse
type-argument@opentelemetry/otlp-exporter-proto-base
package has been removed, and will from now on be deprecated innpm
🚀 (Enhancement)
1.25.0
🚀 (Enhancement)
xray
Propagator viaOTEL_PROPAGATORS
environment variable #4602 @anuraags🐛 (Bug Fix)
getEnv()
andgetEnvWithoutDefaults()
when aprocess
polyfill is used #4648 @pichlermarcgetEnvWithoutDefaults()
would useprocess.env
if it was defined when running in a browser, whilegetEnv()
would always use_globalThis
. Now both use_globalThis
when running in a browser.@opentelemetry/resources