chore(deps): bump the test-versions group across 1 directory with 2 updates

[dependabot]

Bumps the test-versions group with 2 updates in the /packages/dd-trace/test/plugins/versions directory: google-gax and pnpm.

Updates google-gax from 6.7.0 to 6.9.0

Changelog

Sourced from google-gax's changelog.

6.9.0 (2026-09-28)

Features

• gax: Allow customers to enable tracing with environmental variables (#9438) (11d6a6f)
• gax: Differentiate between server side and client side errors (#9451) (c477918)
• gax: Propagate span context to child spans in TracerHelper (#9455) (a6c20e9)
• gax: Support resumable uploads (#9287) (8116709)
• o11y: Remove experimental flag requirement for tracing (#9423) (feb2851)

6.8.0 (2026-09-25)

Features

• gax: Differentiate between server side and client side errors (#9451) (c477918)

Commits

• 27c2f65 chore: release main (#9442)
• a6c20e9 feat(gax): propagate span context to child spans in TracerHelper (#9455)
• 60ef7c1 chore: release google-gax 6.8.0 (#9453)
• c477918 feat(gax): differentiate between server side and client side errors (#9451)
• a428628 test(gax): add showcase harness for resumable uploads (#9288)
• See full diff in compare view

Updates pnpm from 12.7.0 to 12.8.1

Release notes

Sourced from pnpm's releases.

pnpm 12.8.1 fixes pnpm install --frozen-lockfile rejecting lockfiles with injected workspace packages that have peers, restores the executable bit on files of local directory dependencies, makes pnpm dedupe converge, and uses less CPU on many-core machines.

Patch Changes

• pnpm install --frozen-lockfile no longer rejects a freshly generated lockfile when an injected workspace package has peer dependencies #16332.

• Executable files in a file: directory dependency or an injected workspace package keep their executable bit again. Since 12.8.0, pnpm installed these files without the permissions they have in their project.

• pnpm dedupe now reaches a stable lockfile when a package's peer suffix is long enough to be hashed. Before, each run could switch that package's key between the hashed and the spelled-out suffix, so pnpm dedupe --check always failed #16331.

• pnpm install --frozen-lockfile, the default in CI, now uses less CPU on machines with more than 8 cores. Warm installs on many-core Windows machines got up to 10% faster. Frozen installs now link with at most 16 worker threads.

• verifyDepsBeforeRun no longer reports dependencies as outdated after a filtered install just because pnpm-lock.yaml has a newer modification time. It checks the lockfile against the packages that install put in place. Before, pnpm run reinstalled the whole workspace with lifecycle scripts on, for example after a Docker COPY brought in a lockfile with a newer mtime #16322.

  After a filtered install, verifyDepsBeforeRun now also checks that the install put the selected projects' dependencies in place. A node_modules directory alone no longer counts as proof.

• pnpm run and pnpm exec no longer install a project that has never been installed and has nothing to install. Such a project declares no dependencies, no peer dependencies that autoInstallPeers would fetch, and no install lifecycle scripts. The command now runs without writing node_modules or pnpm-lock.yaml #16313.

• pnpm update -g --latest now upgrades globally installed packages beyond their saved version ranges #16320.

Platinum Sponsors

... (truncated)

Commits

• 57e7b9b chore(release): 11.28.2, pacquet 12.8.1 (#16349)
• 9ce8c2e chore(release): 11.28.1, pacquet 12.8.0, pnpr 0.1.0-alpha.14 (#16312)
• 550f9cf fix(npm): point project Windows shims at pnpm.exe (#15714)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dd-octo-sts]

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}

[datadog-datadog-prod-us1-2]

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

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog retried 2 tests - 2 passed on retry

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-10-02 01:26:46

Comparing candidate commit e2b9d8d in PR branch dependabot/npm_and_yarn/packages/dd-trace/test/plugins/versions/test-versions-8aaf3c1f85 with baseline commit 1d0b8c3 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2391 metrics, 12 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-appsec-enabled-24

• unstable max_rss_usage [-19.992MB; +28.834MB] or [-6.963%; +10.042%]

scenario:appsec-appsec-enabled-with-attacks-20

• unstable max_rss_usage [-15.877MB; +25.381MB] or [-9.207%; +14.718%]

scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-20

• unstable max_rss_usage [-52.220MB; +70.968MB] or [-14.692%; +19.966%]

scenario:fs-subscribed-24

• unstable execution_time [-20.720ms; +29.994ms] or [-5.118%; +7.409%]

scenario:llmobs-span-processor-embedding-20

• unstable execution_time [-129.099ms; +190.028ms] or [-5.249%; +7.726%]

scenario:openfeature-scale-full-24

• unstable max_rss_usage [-36.656MB; +10.098MB] or [-12.208%; +3.363%]

scenario:plugin-claude-agent-sdk-compact-stream-scan-26

• unstable execution_time [-211.679ms; +521.690ms] or [-2.968%; +7.314%]

scenario:plugin-graphql-long-with-depth-on-max-26

• unstable cpu_user_time [-404.346ms; +571.730ms] or [-4.994%; +7.062%]
• unstable execution_time [-405.417ms; +575.053ms] or [-4.909%; +6.963%]
• unstable throughput [-14.007op/s; +9.810op/s] or [-6.299%; +4.412%]

scenario:plugin-memcached-get-24

• unstable execution_time [-119.035ms; +183.531ms] or [-4.959%; +7.646%]

scenario:spans-finish-later-26

• unstable max_rss_usage [-5.761MB; +9.273MB] or [-3.874%; +6.237%]