chore(release): prepare dial9-trace-format 0.4.0 breaking release#371
Merged
Conversation
Member
Author
|
Oh, just saw #342 , will try to sweep that in too |
Contributor
|
We should hold off until I patch the lost wake issue in task dumps. If you want to knock it out it's a small fix to not use a no-op waker |
Member
Author
|
Member
Author
|
fine to wait for tomorrow to release this though, i'd rather get in the toolkit improvements and the new tracing visualizations |
rcoh
reviewed
May 8, 2026
| [package] | ||
| name = "dial9-trace-format-derive" | ||
| version = "0.3.5" | ||
| version = "0.3.6" |
Contributor
There was a problem hiding this comment.
I think this needs to go 0.4 because the changes in derive are breaking
rcoh
requested changes
May 8, 2026
rcoh
left a comment
rcoh
left a comment
Contributor
There was a problem hiding this comment.
before we merge this we also should make sure the dial9 readme is very clear to humans and agents (since that crate is what people will find most easily)
| - *(design)* metrique → dial9 integration ([#346](https://github.com/dial9-rs/dial9-tokio-telemetry/pull/346)) | ||
| - Follow up - Expose runtime pipeline ([#365](https://github.com/dial9-rs/dial9-tokio-telemetry/pull/365)) | ||
| - Expose runtime pipeline ([#355](https://github.com/dial9-rs/dial9-tokio-telemetry/pull/355)) | ||
| - Add task dump capture behind taskdump feature ([#354](https://github.com/dial9-rs/dial9-tokio-telemetry/pull/354)) |
Member
Author
jlizen
force-pushed
the
release/dial9-trace-format-0.4.0
branch
from
1106355 to
8480beb
Compare
jlizen
force-pushed
the
release/dial9-trace-format-0.4.0
branch
from
8480beb to
c19802b
Compare
jlizen
force-pushed
the
release/dial9-trace-format-0.4.0
branch
from
c19802b to
216a2d3
Compare
rcoh
approved these changes
May 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cutting a release that has
dial9-trace-formatbreaking, and everything else un-breaking. We did a bunch of semver cleanup along with adding new types (though adding new types won't be breaking in the future).I figure we don't want to keep our main in a confusing state with breaking cargo semver staged in it any longer than we had to.
Though, I'd like to link in #370 if anybody has time for a review, in which case i'll update the changelog accordingly.