chore(deps): bump the databases group across 1 directory with 3 updates

[dependabot]

Bumps the databases group with 3 updates in the /packages/dd-trace/test/plugins/versions directory: @redis/client, bson and redis.

Updates @redis/client from 6.2.0 to 6.2.1

Release notes

Sourced from @​redis/client's releases.

redis@6.2.1

What's Changed

• fix(sentinel): cap post-connect rediscovery retries by @​DebadityaHait in redis/node-redis#3388
• chore(deps): bump ip-address and socks by @​dependabot[bot] in redis/node-redis#3389
• feat(client): add MaxCommandRedirectionsError for cluster redirections by @​Piyush0049 in redis/node-redis#3386
• fix: remove stale data listener explicitly on socket error by @​Chrisp1tv in redis/node-redis#3209
• fix(client): dispose credentials subscription on every close() path by @​lazerg in redis/node-redis#3391
• fix(cluster): keep batch commands routed by slot during migration by @​GiHoon1123 in redis/node-redis#3377
• fix(client): decode RESP3 doubles to the value the server sent by @​Jaybhade in redis/node-redis#3393
• fix(cluster): handle MOVED and ASK redirects for atomic MULTI by @​konovalovsergey in redis/node-redis#3395

New Contributors

• @​DebadityaHait made their first contribution in redis/node-redis#3388
• @​Chrisp1tv made their first contribution in redis/node-redis#3209
• @​lazerg made their first contribution in redis/node-redis#3391
• @​Jaybhade made their first contribution in redis/node-redis#3393
• @​konovalovsergey made their first contribution in redis/node-redis#3395

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.2.0...redis@6.2.1

Commits

• 85d7038 Release json@6.2.1
• 992f068 Release bloom@6.2.1
• 10b5625 Release client@6.2.1
• ba1b90b fix(cluster): handle MOVED and ASK redirects for atomic MULTI (#3395)
• 2f0ab75 fix(client): decode RESP3 doubles to the value the server sent (#3393)
• d4eba09 fix(cluster): keep batch commands routed by slot during migration (#3377)
• 0c03255 fix(client): dispose credentials subscription on every close() path (#3391)
• 2215b5d fix: remove stale data listener explicitly on socket error (#3209)
• e6bd924 feat(client): add MaxCommandRedirectionsError for cluster redirections (#3386)
• 239a6cd chore(deps): bump ip-address and socks (#3389)
• Additional commits viewable in compare view

Updates bson from 7.3.1 to 7.3.2

Release notes

Sourced from bson's releases.

v7.3.2

7.3.2 (2026-07-31)

The MongoDB Node.js team is pleased to announce version 7.3.2 of the bson package!

Release Notes

calculateObjectSize() now returns accurate byte counts for Int32 and BSONSymbol

Previously, each Int32 or BSONSymbol value caused a 12-byte overcount.

calculateObjectSize() now yields proper size calculations on ES Map's

This release of js-bson fixes an issue where we were incorrectly considering ES Map objects inside calculateObjectSize. This issue did not impact serialization, just size calculation.

Fixed incorrect date boundary in relaxed EJSON

This release of js-bson fixes an issue where the date boundary for relaxed EJSON was incorrectly set to a date 5 hours after the maximum limit of 10,000 AD.

Fixed an issue with ObjectId initialization in Cloudflare Workers

This release of js-bson fixes an issue where we were making crypto calls during module initialization, which is forbidden by Cloudflare Workers and other environments.

Memory optimization via smaller ObjectIds

ObjectId now stores its 12 bytes as four inline integers instead of a Uint8Array, cutting per-ObjectId memory by about 63% (and roughly 45 to 47% across large result sets) with no serialization slowdown. Deep equality and cloning are preserved (assert.deepStrictEqual, and lodash isEqual / cloneDeep).

Thanks to @​spokodev for contributing their fixes! (NODE-7631 (#901), NODE-7645 (#917), NODE-7646 (#910))

Bug Fixes

• NODE-7631: count Int32 and BSONSymbol in calculateObjectSize (#901) (7f948a6)
• NODE-7645: use the first instant of year 10000 as the relaxed EJSON date bound (#917) (9272c9a)
• NODE-7646: count ES Map entries in calculateObjectSize (#910) (8d28b12)
• NODE-7667: remove early initialization from ObjectId (#916) (665286f)

Performance Improvements

• NODE-6246: store ObjectId bytes as four packed integers (#893) (a84229c)

Documentation

• API
• Changelog

We invite you to try the bson library immediately, and report any issues to the NODE project.

Changelog

Sourced from bson's changelog.

7.3.2 (2026-07-31)

Bug Fixes

• NODE-7631: count Int32 and BSONSymbol in calculateObjectSize (#901) (7f948a6)
• NODE-7645: use the first instant of year 10000 as the relaxed EJSON date bound (#917) (9272c9a)
• NODE-7646: count ES Map entries in calculateObjectSize (#910) (8d28b12)
• NODE-7667: remove early initialization from ObjectId (#916) (665286f)

Performance Improvements

• NODE-6246: store ObjectId bytes as four packed integers (#893) (a84229c)

Commits

• 9cd2e68 chore(main): release 7.3.2 (#902)
• 9272c9a fix(NODE-7645): use the first instant of year 10000 as the relaxed EJSON date...
• 8d28b12 fix(NODE-7646): count ES Map entries in calculateObjectSize (#910)
• 665286f fix(NODE-7667): remove early initialization from ObjectId (#916)
• 1fc57e4 chore(NODE-7681): allow git fetch for npm12 (#914)
• 57b5bf0 chore: use bundled version of NPM (#913)
• a84229c perf(NODE-6246): store ObjectId bytes as four packed integers (#893)
• 7f948a6 fix(NODE-7631): count Int32 and BSONSymbol in calculateObjectSize (#901)
• See full diff in compare view

Updates redis from 6.2.0 to 6.2.1

Release notes

Sourced from redis's releases.

redis@6.2.1

What's Changed

• fix(sentinel): cap post-connect rediscovery retries by @​DebadityaHait in redis/node-redis#3388
• chore(deps): bump ip-address and socks by @​dependabot[bot] in redis/node-redis#3389
• feat(client): add MaxCommandRedirectionsError for cluster redirections by @​Piyush0049 in redis/node-redis#3386
• fix: remove stale data listener explicitly on socket error by @​Chrisp1tv in redis/node-redis#3209
• fix(client): dispose credentials subscription on every close() path by @​lazerg in redis/node-redis#3391
• fix(cluster): keep batch commands routed by slot during migration by @​GiHoon1123 in redis/node-redis#3377
• fix(client): decode RESP3 doubles to the value the server sent by @​Jaybhade in redis/node-redis#3393
• fix(cluster): handle MOVED and ASK redirects for atomic MULTI by @​konovalovsergey in redis/node-redis#3395

New Contributors

• @​DebadityaHait made their first contribution in redis/node-redis#3388
• @​Chrisp1tv made their first contribution in redis/node-redis#3209
• @​lazerg made their first contribution in redis/node-redis#3391
• @​Jaybhade made their first contribution in redis/node-redis#3393
• @​konovalovsergey made their first contribution in redis/node-redis#3395

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.2.0...redis@6.2.1

Commits

• 90fd065 Release redis@6.2.1
• 9d52256 Release entraid@6.2.1
• 58d2b8a Release time-series@6.2.1
• 7565ac6 Release search@6.2.1
• 85d7038 Release json@6.2.1
• 992f068 Release bloom@6.2.1
• 10b5625 Release client@6.2.1
• ba1b90b fix(cluster): handle MOVED and ASK redirects for atomic MULTI (#3395)
• 2f0ab75 fix(client): decode RESP3 doubles to the value the server sent (#3393)
• d4eba09 fix(cluster): keep batch commands routed by slot during migration (#3377)
• Additional commits viewable in compare view

[dd-octo-sts]

Overall package size

Self size: 8.2 MB
Deduped: 8.86 MB
No deduping: 8.86 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.3 | 125.43 kB | 441.72 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-prod-us1-4]

 

⚠️ Warnings

🚦 2 Pipeline jobs failed

All Green | all-green     

See error

Job did not run: blocked by a failed job in an earlier pipeline stage.

Pull Request Title | conventional-commit     

See error

API rate limit exceeded for installation while trying to retrieve pull request files for PR #9829.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4c8daa6 | Docs | Datadog PR Page | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-17 01:44:03

Comparing candidate commit 4c8daa6 in PR branch dependabot/npm_and_yarn/packages/dd-trace/test/plugins/versions/databases-108850895c with baseline commit 7142bf6 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2283 metrics, 9 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-with-vulnerability-iast-enabled-default-config-20

• unstable max_rss_usage [-23.177MB; +15.357MB] or [-6.034%; +3.998%]

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

• unstable max_rss_usage [-20.709MB; +11.850MB] or [-8.321%; +4.761%]

scenario:dogstatsd-with-tags-20

• unstable cpu_user_time [-236.979ms; +445.262ms] or [-4.956%; +9.312%]
• unstable execution_time [-234.630ms; +447.712ms] or [-4.836%; +9.228%]
• unstable throughput [-158469.528op/s; +82069.714op/s] or [-9.155%; +4.741%]

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

• unstable cpu_usage_percentage [-7.111%; +3.251%]

scenario:plugin-graphql-long-with-depth-and-collapse-off-20

• unstable max_rss_usage [-27.867MB; +18.088MB] or [-6.963%; +4.520%]

scenario:test-optimization-wide-tags-24

• unstable cpu_user_time [-181.237ms; +314.877ms] or [-4.393%; +7.632%]
• unstable execution_time [-183.906ms; +314.623ms] or [-4.420%; +7.561%]