Skip to content
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 1.23.0/0.50.0 #4601

Merged

Conversation

pichlermarc
Copy link
Member

@pichlermarc pichlermarc commented Apr 2, 2024

1.23.0

🚀 (Enhancement)

  • perf(sdk-trace-base): do not allocate arrays if resource has no pending async attributes #4576 @Samuron
  • feat(sdk-metrics): added experimental synchronous gauge to SDK #4565 @clintonb
    • this change will become user-facing in an upcoming release

🐛 (Bug Fix)

  • fix(sdk-metrics): increase the depth of the output to the console such that objects in the metric are printed fully to the console #4522 @JacksonWeber

0.50.0

💥 Breaking Change

  • fix(exporter-*-otlp-grpc)!: lazy load gRPC to improve compatibility with @opentelemetry/instrumenation-grpc #4432 @pichlermarc
    • Fixes a bug where requiring up the gRPC exporter before enabling the instrumentation from @opentelemetry/instrumentation-grpc would lead to missing telemetry
    • Breaking changes, removes several functions and properties that were used internally and were not intended for end-users
      • getServiceClientType()
        • this returned a static enum value that would denote the export type (SPAN, METRICS, LOGS)
      • getServiceProtoPath()
        • this returned a static enum value that would correspond to the gRPC service path
      • metadata
        • was used internally to access metadata, but as a side effect allowed end-users to modify metadata on runtime.
      • serviceClient
        • was used internally to keep track of the service client used by the exporter, as a side effect it allowed end-users to modify the gRPC service client that was used
      • compression
        • was used internally to keep track of the compression to use but was unintentionally exposed to the users. It allowed to read and write the value, writing, however, would have no effect.
  • feat(api-events)!: removed domain from the Events API #4569 @martinkuba
  • fix(api-events)!: renamed EventEmitter to EventLogger in the Events API #4569 @martinkuba
  • feat(api-logs)!: changed LogRecord body data type to AnyValue #4575 @martinkuba
    and AnyValueMap types #4575 @martinkuba

🚀 (Enhancement)

🐛 (Bug Fix)

📚 (Refine Doc)

  • docs(instrumentation-http): document semantic conventions and attributes in use. #4587 @JamieDanielson

Copy link

codecov bot commented Apr 2, 2024

Codecov Report

Merging #4601 (abc91d3) into main (928796d) will increase coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4601      +/-   ##
==========================================
+ Coverage   92.80%   92.81%   +0.01%     
==========================================
  Files         328      328              
  Lines        9512     9512              
  Branches     2047     2047              
==========================================
+ Hits         8828     8829       +1     
+ Misses        684      683       -1     

see 1 file with indirect coverage changes

@pichlermarc pichlermarc marked this pull request as ready for review April 2, 2024 21:10
@pichlermarc pichlermarc requested a review from a team April 2, 2024 21:10
@pichlermarc pichlermarc merged commit 5231aa2 into open-telemetry:main Apr 3, 2024
20 checks passed
@pichlermarc pichlermarc deleted the release/1.23.0-0.50.0 branch April 3, 2024 07:57
Zirak pushed a commit to Zirak/opentelemetry-js that referenced this pull request Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants