Skip to content

Conversation

@tisonkun
Copy link
Contributor

This closes #2665

@tisonkun tisonkun requested a review from a team as a code owner February 14, 2025 13:03
@codecov
Copy link

codecov bot commented Feb 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.1%. Comparing base (cd9bbcf) to head (243445d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #2666   +/-   ##
=====================================
  Coverage   79.1%   79.1%           
=====================================
  Files        122     122           
  Lines      22562   22562           
=====================================
+ Hits       17861   17862    +1     
+ Misses      4701    4700    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cijothomas cijothomas merged commit 32a43ca into open-telemetry:main Feb 14, 2025
21 checks passed
@tisonkun tisonkun deleted the drop-axum-deps branch February 14, 2025 15:18
@tisonkun
Copy link
Contributor Author

@cijothomas may I ask when is the next release expected out? I'd make a corresponding expectation for upgrading my project later or patch it right now.

@cijothomas
Copy link
Member

~2 weeks (https://github.com/open-telemetry/opentelemetry-rust/milestone/19)
if there is enough demand, we can always do a .1 release for OTLP Exporter any time.

cijothomas pushed a commit to cijothomas/opentelemetry-rust that referenced this pull request Feb 18, 2025
@neoeinstein
Copy link
Contributor

I'd be interested in a .1 release, as it seems like 0.29 is still a little ways away.

@cijothomas
Copy link
Member

I'd be interested in a .1 release, as it seems like 0.29 is still a little ways away.

Will check in tomorrow's community call about 0.29 release date. I expect to land it soon, but if it is not happening in a month or so, agree .1 is best.

@tisonkun
Copy link
Contributor Author

I'd be interested in a .1 release, as it seems like 0.29 is still a little ways away.

Will check in tomorrow's community call about 0.29 release date. I expect to land it soon, but if it is not happening in a month or so, agree .1 is best.

Any update here?

@cijothomas
Copy link
Member

I'd be interested in a .1 release, as it seems like 0.29 is still a little ways away.

Will check in tomorrow's community call about 0.29 release date. I expect to land it soon, but if it is not happening in a month or so, agree .1 is best.

Any update here?

0.29 release will be this week! Won't be doing .1 because of that. (Missed to updated back in this thread)

@tisonkun
Copy link
Contributor Author

Cool! Thanks for your information :D

@tisonkun
Copy link
Contributor Author

@cijothomas It's Friday, Captain 😆

@cijothomas
Copy link
Member

@cijothomas It's Friday, Captain 😆

🥳 Yaay!

(I'll be starting release process shortly and publish by EOD)

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.

Why axum always in dependency tree?

5 participants