fix(ci): handle proc-macro crates during semver check

[hoolioh]

What does this PR do?

1. libdd-ipc-macros introduced a new crate type and cargo-semver-check tool is unable to handle these type of crates properly. This PR extracts that information from the crate's metadata and select the proper to tool to inspect the changes, in this case cargo-public-api.
2. Fixes a race problem when labels are applied to PRs where a job, that is supposed to be skipped, can be run in the interim between PR creation and label setting.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 696f06e2cc

ℹ️ 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".

[datadog-datadog-us1-prod]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 76.71% (+0.12%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9c4566b | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.52 MB	89.52 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.26 MB	8.26 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.06 MB	0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.70 MB	100.70 MB	0% (0 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.64 MB	26.64 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	180.73 MB	180.73 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	772.85 MB	772.85 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.73 MB	8.73 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.65 MB	25.65 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.09 MB	51.09 MB	0% (0 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.22 MB	23.22 MB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	185.62 MB	185.66 MB	+.02% (+40.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	759.09 MB	759.09 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.74 MB	6.74 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.59 MB	27.59 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.62 MB	48.62 MB	0% (0 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.78 MB	79.78 MB	0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.16 MB	9.16 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.42 MB	95.42 MB	0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.17 MB	11.17 MB	0% (0 B) 👌

[pr-commenter]

Benchmarks

Comparison

Benchmark execution time: 2026-08-27 13:19:12

Comparing candidate commit 9c4566b in PR branch julio/fix-proc-macro-crates with baseline commit 7327f30 in branch main.

Found 13 performance improvements and 10 performance regressions! Performance is the same for 129 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...

• 🟩 execution_time [-19.335µs; -19.179µs] or [-9.419%; -9.343%]
• 🟩 throughput [+502290.125op/s; +506324.916op/s] or [+10.311%; +10.393%]

scenario:normalization/normalize_name/normalize_name/bad-name

• 🟩 execution_time [-1.811µs; -1.734µs] or [-9.440%; -9.042%]
• 🟩 throughput [+5194227.822op/s; +5422218.220op/s] or [+9.962%; +10.399%]

scenario:normalization/normalize_name/normalize_name/good

• 🟩 execution_time [-1.233µs; -1.188µs] or [-11.180%; -10.774%]
• 🟩 throughput [+10978851.210op/s; +11385038.439op/s] or [+12.104%; +12.552%]

scenario:normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...

• 🟩 execution_time [-36.777µs; -36.498µs] or [-6.872%; -6.820%]
• 🟩 throughput [+136791.115op/s; +137849.070op/s] or [+7.321%; +7.377%]

scenario:normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters

• 🟩 execution_time [-21.370µs; -21.240µs] or [-11.201%; -11.134%]
• 🟩 throughput [+656996.849op/s; +660905.500op/s] or [+12.534%; +12.609%]

scenario:otlp/e2e_json/1x1000

• 🟥 execution_time [+332.081µs; +333.350µs] or [+8.078%; +8.108%]

scenario:otlp/encode_json/1x1000

• 🟥 execution_time [+295.482µs; +296.178µs] or [+16.172%; +16.210%]

scenario:otlp/encode_protobuf/1x1000

• 🟩 execution_time [-52.103µs; -51.788µs] or [-4.680%; -4.652%]

scenario:sdk_test_data/rules-based

• 🟩 execution_time [-117.519µs; -113.569µs] or [-44.748%; -43.244%]

scenario:vec_map/as_deduped_map/already_deduped/8

• 🟥 execution_time [+0.585ns; +0.605ns] or [+4.210%; +4.354%]

scenario:vec_map/get_miss/16

• 🟩 execution_time [-0.919ns; -0.759ns] or [-9.000%; -7.427%]

scenario:vec_map/get_miss/8

• 🟥 execution_time [+1.761ns; +1.792ns] or [+30.659%; +31.199%]

scenario:vec_map/get_mut/128

• 🟥 execution_time [+1.891µs; +1.994µs] or [+13.439%; +14.172%]
• 🟥 throughput [-1133102.949op/s; -1073307.626op/s] or [-12.454%; -11.797%]

scenario:vec_map/get_mut/16

• 🟥 execution_time [+14.792ns; +23.643ns] or [+5.400%; +8.631%]
• 🟥 throughput [-4859099.999op/s; -2978805.453op/s] or [-8.260%; -5.064%]

scenario:vec_map/get_mut/64

• 🟥 execution_time [+456.686ns; +491.962ns] or [+11.717%; +12.622%]
• 🟥 throughput [-1850110.812op/s; -1714714.509op/s] or [-11.262%; -10.438%]

Benchmark execution time: 2026-08-27 13:26:09

Comparing candidate commit 9c4566b in PR branch julio/fix-proc-macro-crates with baseline commit 7327f30 in branch main.

Found 11 performance improvements and 2 performance regressions! Performance is the same for 155 metrics, 10 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:alloc_free/system/4096

• 🟥 execution_time [+13.832ns; +14.045ns] or [+15.132%; +15.365%]

scenario:datadog_sample_span/parent_not_sampled_short_circuit/wall_time

• 🟩 execution_time [-0.407ns; -0.402ns] or [-4.393%; -4.339%]

scenario:datadog_sample_span/parent_sampled_short_circuit/wall_time

• 🟩 execution_time [-0.404ns; -0.399ns] or [-4.362%; -4.313%]

scenario:ddsketch_add/add/large_values

• 🟩 execution_time [-6.224µs; -5.461µs] or [-4.961%; -4.352%]
• 🟩 throughput [+1478819.432op/s; +1679303.630op/s] or [+4.528%; +5.142%]

scenario:ddsketch_add/add_with_count/large_values

• 🟩 execution_time [-7.424µs; -6.538µs] or [-5.755%; -5.068%]
• 🟩 throughput [+1688899.220op/s; +1907264.082op/s] or [+5.316%; +6.003%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

• 🟩 execution_time [-21.578ns; -21.554ns] or [-36.925%; -36.884%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

• 🟩 execution_time [-21.623ns; -21.602ns] or [-36.993%; -36.957%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

• 🟥 execution_time [+3.806ns; +3.950ns] or [+4.217%; +4.377%]

scenario:no_profiler/short_circuit/4096

• 🟩 execution_time [-8.949ns; -8.792ns] or [-8.754%; -8.600%]

scenario:trace_buffer/2_senders/no_delay

• 🟩 execution_time [-166.508µs; -153.272µs] or [-9.888%; -9.102%]
• 🟩 throughput [+107650.711op/s; +116916.425op/s] or [+10.067%; +10.934%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

[ekump]

The codex comments are legit, but non-blocking. Otherwise LGTM