Skip to content

feat(rc): Handle expired config status - #2274

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
mainfrom
bob/expired
Jul 28, 2026
Merged

gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
mainfrom
bob/expired

Conversation

@bwoebi

@bwoebi bwoebi commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Drop all RC files when they expire.

Adds the equivalent capability of DataDog/dd-trace-py@bc2b16b.

Drop all RC files when they expire.

Signed-off-by: Bob Weinand <bob.weinand@datadoghq.com>
@bwoebi
bwoebi requested review from a team as code owners July 24, 2026 18:14
@bwoebi bwoebi changed the title Handle expired config status feat(rc): Handle expired config status Jul 24, 2026

@datadog-prod-us1-3 datadog-prod-us1-3 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: PASS

More details

The expiration path clears the shared remote-config index and the client’s applied paths before returning an empty generation, and the shared fetch loop releases the previous generation on that result. No concrete diff-only behavioral regression was identified; targeted execution was blocked by the sandbox’s unavailable pinned Cargo git dependency.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Datadog Autotest · Commit a3e567e · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3e567e2ce

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"Agent served remote config from an expired cache for target {target:?}, \
dropping all stored configurations"
);
self.state.target_files_by_path.lock_or_panic().clear();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve shared fetcher ownership when expiring configs

When one SharedFetcher in a MultiTargetFetcher receives CONFIG_STATUS_EXPIRED, clearing this shared map immediately bypasses RefcountingStorage's ownership/inactive-file path. If another target still holds the old Arc in its last_files or has an in-flight request that advertised the file as cached, its next OK response sees an empty map and can try to store the same path before the old handle is expired, or fail with Found ... in client_configs response, but it isn't stored; either way that target can keep serving stale expired config. Expiry needs to go through the shared refcount/inactive mechanism or otherwise coordinate all shared runners before dropping the map.

Useful? React with 👍 / 👎.

@datadog-prod-us1-3

datadog-prod-us1-3 Bot commented Jul 24, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 74.77% (+0.17%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 430f1a9 | Docs | Datadog PR Page | Give us feedback!

@pr-commenter

pr-commenter Bot commented Jul 24, 2026

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-07-28 13:16:33

Comparing candidate commit 430f1a9 in PR branch bob/expired with baseline commit 95610de in branch main.

Found 14 performance improvements and 10 performance regressions! Performance is the same for 118 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_service/normalize_service/[empty string]

  • 🟩 execution_time [-2.710µs; -2.684µs] or [-7.088%; -7.022%]
  • 🟩 throughput [+1976531.442op/s; +1994995.456op/s] or [+7.555%; +7.626%]

scenario:otlp/e2e_json/1x1000

  • 🟥 execution_time [+363.411µs; +365.185µs] or [+8.869%; +8.913%]

scenario:otlp/encode_json/1x1000

  • 🟥 execution_time [+351.317µs; +352.151µs] or [+19.753%; +19.800%]

scenario:otlp/encode_protobuf/1x1000

  • 🟩 execution_time [-47.779µs; -47.404µs] or [-4.319%; -4.285%]

scenario:vec_map/as_deduped_map/already_deduped/8

  • 🟥 execution_time [+0.852ns; +0.894ns] or [+5.750%; +6.031%]

scenario:vec_map/get_hit/128

  • 🟩 execution_time [-4.028µs; -4.019µs] or [-24.381%; -24.329%]
  • 🟩 throughput [+2491727.410op/s; +2497350.053op/s] or [+32.161%; +32.233%]

scenario:vec_map/get_hit/16

  • 🟩 execution_time [-37.407ns; -37.174ns] or [-14.982%; -14.888%]
  • 🟩 throughput [+11213335.266op/s; +11290096.350op/s] or [+17.498%; +17.618%]

scenario:vec_map/get_hit/64

  • 🟩 execution_time [-1.011µs; -1.008µs] or [-23.157%; -23.066%]
  • 🟩 throughput [+4395738.445op/s; +4412468.864op/s] or [+30.001%; +30.115%]

scenario:vec_map/get_hit/8

  • 🟩 execution_time [-5.267ns; -5.104ns] or [-7.935%; -7.691%]
  • 🟩 throughput [+10055638.262op/s; +10396332.601op/s] or [+8.343%; +8.625%]

scenario:vec_map/get_miss/128

  • 🟥 execution_time [+3.980ns; +4.167ns] or [+5.182%; +5.427%]

scenario:vec_map/get_miss/16

  • 🟩 execution_time [-18.314ns; -17.994ns] or [-66.497%; -65.334%]

scenario:vec_map/get_miss/64

  • 🟩 execution_time [-22.400ns; -22.335ns] or [-43.916%; -43.788%]

scenario:vec_map/get_miss/8

  • 🟩 execution_time [-10.851ns; -10.650ns] or [-59.434%; -58.330%]

scenario:vec_map/get_mut/128

  • 🟥 execution_time [+2.173µs; +2.264µs] or [+15.902%; +16.574%]
  • 🟥 throughput [-1338178.030op/s; -1281321.936op/s] or [-14.279%; -13.673%]

scenario:vec_map/get_mut/16

  • 🟥 execution_time [+19.447ns; +30.039ns] or [+7.016%; +10.838%]
  • 🟥 throughput [-5947912.751op/s; -3776792.249op/s] or [-10.203%; -6.479%]

scenario:vec_map/get_mut/64

  • 🟥 execution_time [+457.521ns; +498.199ns] or [+11.901%; +12.960%]
  • 🟥 throughput [-1926657.535op/s; -1764638.447op/s] or [-11.564%; -10.591%]

Benchmark execution time: 2026-07-28 13:32:02

Comparing candidate commit 430f1a9 in PR branch bob/expired with baseline commit 95610de in branch main.

Found 24 performance improvements and 6 performance regressions! Performance is the same for 147 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/sampled_system_fast_path/16

  • 🟩 execution_time [-3.965ns; -3.857ns] or [-13.328%; -12.964%]

scenario:alloc_free/sampled_system_fast_path/256

  • 🟩 execution_time [-3.939ns; -3.871ns] or [-13.239%; -13.010%]

scenario:alloc_free/sampled_system_fast_path/64

  • 🟩 execution_time [-3.917ns; -3.855ns] or [-13.166%; -12.958%]

scenario:alloc_free/sampled_system_slow_path/4096

  • 🟩 execution_time [-10.923ns; -10.827ns] or [-6.918%; -6.857%]

scenario:alloc_free/system/16

  • 🟥 execution_time [+1.118ns; +1.167ns] or [+7.805%; +8.148%]

scenario:alloc_free/system/256

  • 🟥 execution_time [+1.126ns; +1.171ns] or [+7.869%; +8.183%]

scenario:alloc_free/system/64

  • 🟥 execution_time [+0.962ns; +1.013ns] or [+6.723%; +7.083%]

scenario:credit_card/is_card_number/ 378282246310005

  • 🟩 execution_time [-5.482µs; -5.376µs] or [-7.433%; -7.289%]
  • 🟩 throughput [+1067327.490op/s; +1087023.813op/s] or [+7.871%; +8.016%]

scenario:credit_card/is_card_number/378282246310005

  • 🟩 execution_time [-5.702µs; -5.611µs] or [-8.053%; -7.924%]
  • 🟩 throughput [+1216708.130op/s; +1235019.232op/s] or [+8.615%; +8.745%]

scenario:credit_card/is_card_number/37828224631000521389798

  • 🟩 execution_time [-7.295µs; -7.239µs] or [-13.761%; -13.656%]
  • 🟩 throughput [+2985052.586op/s; +3008910.603op/s] or [+15.824%; +15.950%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

  • 🟩 execution_time [-4.955µs; -4.912µs] or [-8.478%; -8.404%]
  • 🟩 throughput [+1571033.550op/s; +1583940.053op/s] or [+9.181%; +9.257%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

  • 🟩 execution_time [-5.274µs; -5.223µs] or [-9.498%; -9.406%]
  • 🟩 throughput [+1871403.063op/s; +1888276.981op/s] or [+10.391%; +10.484%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

  • 🟩 execution_time [-7.410µs; -7.354µs] or [-13.941%; -13.836%]
  • 🟩 throughput [+3022263.929op/s; +3047273.730op/s] or [+16.063%; +16.196%]

scenario:datadog_sample_span/name_pattern_rule_not_matching/wall_time

  • 🟥 execution_time [+37.097ns; +37.203ns] or [+23.618%; +23.686%]

scenario:ddsketch_encode/encode_to_vec/clustered_near_zero

  • 🟩 execution_time [-44.762ns; -39.729ns] or [-6.001%; -5.327%]

scenario:ddsketch_encode/encode_to_vec/large_values

  • 🟩 execution_time [-65.861ns; -60.359ns] or [-7.253%; -6.647%]

scenario:ddsketch_encode/encode_to_vec/mixed

  • 🟩 execution_time [-81.783ns; -74.735ns] or [-6.233%; -5.696%]

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

  • 🟩 execution_time [-2.655ns; -2.629ns] or [-9.053%; -8.965%]

scenario:glob_matcher/ascii_exact_match/wall_time

  • 🟩 execution_time [-2.642ns; -2.612ns] or [-9.011%; -8.910%]

scenario:glob_matcher/ascii_exact_miss/wall_time

  • 🟩 execution_time [-2.525ns; -2.465ns] or [-17.891%; -17.470%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

  • 🟩 execution_time [-21.117ns; -21.095ns] or [-36.431%; -36.394%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

  • 🟩 execution_time [-22.727ns; -22.708ns] or [-37.684%; -37.652%]

scenario:trace_buffer/4_senders/no_delay

  • 🟥 execution_time [+137.070µs; +168.335µs] or [+5.992%; +7.359%]
  • 🟥 throughput [-109721.220op/s; -89034.325op/s] or [-6.962%; -5.649%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@dd-octo-sts

dd-octo-sts Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 8.01 MB 8.01 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 87.13 MB 87.13 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.77 MB 10.77 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 98.38 MB 98.38 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 26.00 MB 26.00 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 89.18 KB 89.18 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 187.92 MB 187.93 MB +0% (+8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 978.93 MB 978.93 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.47 MB 8.47 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 89.18 KB 89.18 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 25.05 MB 25.05 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 49.84 MB 49.84 MB 0% (0 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 22.61 MB 22.61 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 90.58 KB 90.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 192.53 MB 192.51 MB -0% (-16.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 968.13 MB 968.13 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.54 MB 6.54 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 90.58 KB 90.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 26.91 MB 26.91 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 47.43 MB 47.43 MB 0% (0 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 77.73 MB 77.73 MB 0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 8.91 MB 8.91 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 93.20 MB 93.20 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.84 MB 10.84 MB 0% (0 B) 👌

Signed-off-by: Bob Weinand <bob.weinand@datadoghq.com>
@bwoebi

bwoebi commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jul 28, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-07-28 13:34:23 UTC ℹ️ Start processing command /merge


2026-07-28 13:34:32 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2026-07-28 13:39:24 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 1h (p90).


2026-07-28 14:23:18 UTC ℹ️ MergeQueue: This merge request was merged

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 4a0e5bc into main Jul 28, 2026
112 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the bob/expired branch July 28, 2026 14:23
hoolioh added a commit that referenced this pull request Aug 7, 2026
…er-flare (#2332)

# Release proposal for libdd-ffe, libdd-http-client, libdd-tracer-flare
and their dependencies

This PR contains version bumps based on public API changes and commits
since last release.

## libdd-capabilities
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-v3.0.0`

### Commits

- fix(telemetry)!: stop sending Connection: close to the Agent (#2286)
- feat(capabilities)!: Add streaming to http capabilities (#2251)
- feat: added file capability [APMSP-3780] (#2240)
- feat: added environment capability [APMSP-3780] (#2239)

## libdd-common
**Next version:** `5.1.1`
**Semver bump:** `patch`
**Tag:** `libdd-common-v5.1.1`

### Commits

- feat(telemetry)!: Add Installation signature and AppProduct changes
payloads (#2213)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- test: stabilize flaky tests (#2256)
- fix(sidecar): don't double-encode file:// telemetry endpoints (#2230)
- fix: last new clippy lint (#2221)

## libdd-tinybytes
**Next version:** `1.1.2`
**Semver bump:** `patch`
**Tag:** `libdd-tinybytes-v1.1.2`

### Commits

- chore: moving to workspace-level dependencies, phase 2 (#2270)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)

## libdd-trace-protobuf
**Next version:** `4.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-trace-protobuf-v4.0.1`

### Commits

- refactor: migrate to workspace dependencies, phase 4 (#2296)
- chore: moving to workspace-level dependencies, phase 2 (#2270)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- feat(stats)!: implement additional metric tags in libdd-trace-stats
(#2170)

## libdd-capabilities-impl
**Next version:** `4.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-impl-v4.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^2.1.0 → ^3.0.0

### Commits

- feat(telemetry)!: Add Installation signature and AppProduct changes
payloads (#2213)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- fix(telemetry)!: stop sending Connection: close to the Agent (#2286)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- feat(capabilities)!: Add streaming to http capabilities (#2251)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- feat: added file capability [APMSP-3780] (#2240)
- feat(telemetry)!: make telemetry worker wasm-compatible for the
TraceExporter (#2172)
- feat: added environment capability [APMSP-3780] (#2239)

## libdd-http-client
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-http-client-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


## libdd-trace-normalization
**Next version:** `3.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-trace-normalization-v3.0.1`

### Commits

- refactor: migrate to workspace dependencies, phase 4 (#2296)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)

## libdd-remote-config
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-remote-config-v3.0.0`

### Commits

- refactor(rc)!: make conversion from RemoteConfigProduct back and forth
generally available (#2325)
- fix(wasm)!: finish the WASM port of remote-config (#2315)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- feat(rc): Handle expired config status (#2274)
- feat(remote-config)!: add AsmRawResponseBody capability (#2278)
- chore: moving to workspace-level dependencies, phase 2 (#2270)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- fix(rc): Make Target fields available again after eaf5ad0 (#2232)
- fix: new clippy lints (#2219)

## libdd-trace-utils
**Next version:** `10.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-utils-v10.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^2.1.0 → ^3.0.0

### Commits

- refactor(rc)!: make conversion from RemoteConfigProduct back and forth
generally available (#2325)
- fix(libdd-trace-utils): apply SpanLink flags masking when v0.5 json
encoding (#2314)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- feat(data-pipeline)!: add compression option for agentless export
(#2205)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- refactor(trace-utils)!: split generic TracerHeaderTags (#2279)
- chore(lint): update nightly (#2281)
- chore: moving to workspace-level dependencies, phase 2 (#2270)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- feat(stats)!: implement additional metric tags in libdd-trace-stats
(#2170)
- feat(trace-utils)!: add v1 decoder (#2174)
- feat(trace-utils)!: add encoder v1 to v04 + refactor (#2145)
- feat(otlp): add instrumentation scope metadata (#2235)
- fix(trace-utils)!: serialize v0.5 span links and events into meta
(#980)

## libdd-ffe
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-ffe-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


## libdd-tracer-flare
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-tracer-flare-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: hoolioh <107922352+hoolioh@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants