Skip to content

ci: update one-pipeline version - #10610

Merged
BridgeAR merged 1 commit into
masterfrom
campaigner/update-one-pipeline
Oct 5, 2026
Merged

BridgeAR merged 1 commit into
masterfrom
campaigner/update-one-pipeline

Conversation

@gh-worker-campaigns-3e9aa4

Copy link
Copy Markdown
Contributor

This automated pull request updates one-pipeline to the latest version.

📝 Full release notes

@dd-octo-sts

dd-octo-sts Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Overall package size

Self size: 9.4 MB
Deduped: 10.14 MB
No deduping: 10.14 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.5.1 | 127.66 kB | 513.61 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@codecov

codecov Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.86%. Comparing base (12f1764) to head (7da3fd2).

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #10610       +/-   ##
===========================================
+ Coverage   88.65%   98.86%   +10.21%     
===========================================
  Files        1047     1057       +10     
  Lines      165990   170911     +4921     
  Branches       74       74               
===========================================
+ Hits       147151   168970    +21819     
+ Misses      18839     1941    -16898     
Flag Coverage Δ
ai-guard 63.92% <ø> (-0.02%) ⬇️
apm-capabilities 54.77% <ø> (ø)
apm-integrations 81.14% <ø> (-0.02%) ⬇️
appsec 57.94% <ø> (-0.01%) ⬇️
debugger 69.58% <ø> (-0.02%) ⬇️
instrumentation 55.40% <ø> (-0.01%) ⬇️
llmobs 80.60% <ø> (-0.02%) ⬇️
master-coverage 98.86% <ø> (?)
openfeature 67.49% <ø> (-0.03%) ⬇️
platform 68.70% <ø> (-0.01%) ⬇️
profiling 66.13% <ø> (-0.03%) ⬇️
serverless 65.69% <ø> (-0.02%) ⬇️
test-optimization 81.99% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@datadog-official

datadog-official Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Tests

✅ All CI checks and tests passed. Datadog automation helped this PR pass.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog retried 3 tests - 3 passed on retry View in Datadog

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 98.26% (+9.65%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7da3fd2 | Docs | View more details | Give us feedback!

@pr-commenter

pr-commenter Bot commented Oct 2, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-10-02 16:52:00

Comparing candidate commit 7da3fd2 in PR branch campaigner/update-one-pipeline with baseline commit 12f1764 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2389 metrics, 14 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 ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:appsec-iast-no-vulnerability-iast-enabled-default-config-24

  • unstable max_rss_usage [-24.521MB; +10.433MB] or [-7.519%; +3.199%]

scenario:debugger-line-probe-with-snapshot-minimal-26

  • unstable max_rss_usage [-9840.853KB; +9505.853KB] or [-6.042%; +5.836%]

scenario:debugger-line-probe-without-snapshot-24

  • unstable cpu_user_time [-790.605ms; +1654.144ms] or [-8.455%; +17.691%]
  • unstable execution_time [-821.404ms; +1690.083ms] or [-7.842%; +16.136%]
  • unstable throughput [-178.682op/s; +88.753op/s] or [-16.334%; +8.113%]

scenario:debugger-line-probe-without-snapshot-26

  • unstable cpu_user_time [-584.042ms; +552.766ms] or [-6.696%; +6.338%]
  • unstable execution_time [-585.200ms; +560.832ms] or [-5.943%; +5.695%]
  • unstable throughput [-68.812op/s; +70.891op/s] or [-5.952%; +6.132%]

scenario:encoders-0.4-immediate-flush-20

  • unstable max_rss_usage [-2.151MB; +7.005MB] or [-2.533%; +8.251%]

scenario:log-with-debug-20

  • unstable max_rss_usage [-8.324MB; +5.399MB] or [-7.219%; +4.682%]

scenario:openfeature-scale-full-24

  • unstable max_rss_usage [-21336.983KB; +23165.983KB] or [-7.275%; +7.898%]

scenario:plugin-aws-sdk-extract-response-body-26

  • unstable execution_time [-245.618ms; +437.545ms] or [-4.883%; +8.698%]
  • unstable throughput [-392817.356op/s; +220612.319op/s] or [-7.141%; +4.011%]

scenario:spans-finish-later-26

  • unstable max_rss_usage [-6.865MB; +13.835MB] or [-4.567%; +9.203%]

@BridgeAR
BridgeAR merged commit 36d3463 into master Oct 5, 2026
724 of 725 checks passed
@BridgeAR
BridgeAR deleted the campaigner/update-one-pipeline branch October 5, 2026 10:17
dd-octo-sts Bot pushed a commit that referenced this pull request Oct 6, 2026
Co-authored-by: gh-worker-campaigns-3e9aa4[bot] <244854796+gh-worker-campaigns-3e9aa4[bot]@users.noreply.github.com>
@dd-octo-sts dd-octo-sts Bot mentioned this pull request Oct 6, 2026
dd-octo-sts Bot pushed a commit that referenced this pull request Oct 6, 2026
Co-authored-by: gh-worker-campaigns-3e9aa4[bot] <244854796+gh-worker-campaigns-3e9aa4[bot]@users.noreply.github.com>
@dd-octo-sts dd-octo-sts Bot mentioned this pull request Oct 6, 2026
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.

1 participant