refactor(datadog-ffe)!: rename crate so it can be published to crates.io - #2285
refactor(datadog-ffe)!: rename crate so it can be published to crates.io#2285hoolioh wants to merge 14 commits into
Conversation
Clippy Allow Annotation ReportTracked Clippy
By file and crateBy file
By crate
About This ReportThis report tracks Clippy allow annotations for specific rules, showing how they've changed in this PR. Decreasing the number of these annotations generally improves code quality. Panic-inducing macros in particular should be avoided. In the future, this report may become a PR-blocking quality gate. |
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: e9949e8 | Docs | Datadog PR Page | Give us feedback! |
BenchmarksComparisonBenchmark execution time: 2026-07-31 08:44:16 Comparing candidate commit e9949e8 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 140 metrics, 0 unstable metrics.
|
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
b5b9efa to
3a48c64
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f05567da39
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
f05567d to
560c605
Compare
560c605 to
f8b548b
Compare
📚 Documentation Check Results📦
|
🔒 Cargo Deny Results📦
|
| name = "datadog-ffe" | ||
| version = "1.0.0" | ||
| name = "libdd-ffe" | ||
| version = "0.1.0" |
There was a problem hiding this comment.
major: any reason this is downgraded to sub 1?
There was a problem hiding this comment.
It's to avoid that the release system will publish a 2.0.0 version. The release system works on the assumption that every crate on the workspace stays in beta until it's published because it doesn't track which crates are published and which aren't so if I leave the 1.0.0 the system will bump the major and a 2.0.0 version will appear as a the first release in crates.io.
It's something we could improve in the future though
There was a problem hiding this comment.
Then we need to decrease libdd-ffe-ffi crate version as well?
There was a problem hiding this comment.
It's not needed, at the moment, we're not publishing the ffi crates since the ffi library is consumed via the released artifacts or by tag reference to libdd-profiling-ffi crate (which is the one that manages the inclusion of the rest of the crates).
In the future if we publish the ffi crates we will need to do it but we're in thinking about how to rearchitecture the whole thing.
What does this PR do?
This PR makes the proper changes to publish FFE crate, for that the crate name has to be renamed in order to adhere to the repo publishing policies and dependants references updated.
Motivation
Allow downstream projects to use independent versions.