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

[dependabot]

Bumps the databases group with 8 updates in the /packages/dd-trace/test/plugins/versions directory:

Package	From	To
@prisma/adapter-mariadb	7.9.1	7.10.0
@prisma/adapter-mssql	7.9.1	7.10.0
@prisma/adapter-pg	7.9.1	7.10.0
@prisma/client	7.9.1	7.10.0
mongoose	9.9.3	9.9.4
mysql2	3.23.4	3.24.2
prisma	7.9.1	7.10.0
sharedb	6.0.1	6.0.2

Updates @prisma/adapter-mariadb from 7.9.1 to 7.10.0

Release notes

Sourced from @​prisma/adapter-mariadb's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• See full diff in compare view

Updates @prisma/adapter-mssql from 7.9.1 to 7.10.0

Release notes

Sourced from @​prisma/adapter-mssql's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• See full diff in compare view

Updates @prisma/adapter-pg from 7.9.1 to 7.10.0

Release notes

Sourced from @​prisma/adapter-pg's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• a180209 fix(adapter-pg): map PostgreSQL deadlocks to P2034 (#29717)
• 800f1d1 fix(adapter-pg): preserve constraint name for unique violations (23505) (#29587)
• 7ef2104 fix(postgres): handle SQLSTATE 23001 for RESTRICT violations (#29554)
• See full diff in compare view

Updates @prisma/client from 7.9.1 to 7.10.0

Release notes

Sourced from @​prisma/client's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 05c1b88 Teach Prisma 7 to prefer versioned config files (#30020)
• cf2bc1f Rename prisma7 package to @​prisma/prisma7 (#30002)
• ce5a34c Complete downstream actionable Prisma 7 guidance propagation (#29994)
• 3f13ec6 Complete CLI-owned prisma7 distribution identity (#29969)
• 179ba0c feat(prisma7): add side-by-side CLI wrapper (#29949)
• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• 6b6d9e9 chore(deps): update engines to 7.10.0-4.0edf323efd1d98336f3f0a68684b56f689b90...
• b64e33c chore(deps): update engines to 7.10.0-3.9d90ce2c89d5c95a1148aef15e5561ab6c490...
• 2046f9b feat(client): expose ModelName to compute function in Result extensions (#29782)
• f2b3abd chore(deps): update engines to 7.10.0-1.6d040c802892de6d56c7e0061b7a10b3e6a0c...
• Additional commits viewable in compare view

Updates mongoose from 9.9.3 to 9.9.4

Release notes

Sourced from mongoose's releases.

9.9.4 / 2026-08-25

• fix(query): set strictQuery and strict on _mongooseOptions consistently #16451 #16447
• fix(hydration): use the doc model for looking up a ref #16453 rawmind
• fix(schema): drop the map values subpath when removing a map path #16457 rawmind
• fix(schema): remove a map that lives under a nested path #16461 #16457 luantaraschi
• fix(schema): do not repeat null in a toJSONSchema enum that already lists null #16456 luantaraschi
• fix(schema): clone a document array element with its own constructor signature #16463 #16462 luantaraschi
• fix(schema): keep the map value schematype a single object when cloning #16473 luantaraschi
• fix(schema): clarify duplicate index warning to note index is not created #16476 vjymisal0
• perf(model): index bulkSave write errors by document id #16474 yoominho91
• docs: add Atlas Vector Search and Atlas Search documentation #16395
• docs: fix dead MongoDB driver Collection link #16458 rajanpanth

Changelog

Sourced from mongoose's changelog.

9.9.4 / 2026-08-25

• fix(query): set strictQuery and strict on _mongooseOptions consistently #16451 #16447
• fix(hydration): use the doc model for looking up a ref #16453 rawmind
• fix(schema): drop the map values subpath when removing a map path #16457 rawmind
• fix(schema): remove a map that lives under a nested path #16461 #16457 luantaraschi
• fix(schema): do not repeat null in a toJSONSchema enum that already lists null #16456 luantaraschi
• fix(schema): clone a document array element with its own constructor signature #16463 #16462 luantaraschi
• fix(schema): keep the map value schematype a single object when cloning #16473 luantaraschi
• fix(schema): clarify duplicate index warning to note index is not created #16476 vjymisal0
• perf(model): index bulkSave write errors by document id #16474 yoominho91
• docs: add Atlas Vector Search and Atlas Search documentation #16395
• docs: fix dead MongoDB driver Collection link #16458 rajanpanth

8.24.4 / 2026-08-21

• fix(discriminator): prevent indexes and callQueue duplication with shared nested schemas #16467 #16466 #15966 (8.x backport) AbinMadathil-Celigo

Commits

• a4b8a60 chore: release 9.9.4
• 9ffac59 Merge pull request #16474 from yoominho91/perf/bulksave-error-index
• e57f554 Merge pull request #16478 from vjymisal0/fix/duplicate-index-warning-message
• aa68225 docs: fix markdown lint
• e3b2db6 Merge pull request #16395 from RaschidJFR/docs/mongodb-sync-20260708-151113
• e76ea0a Clarify embedded_movies collection usage
• 72c9d59 Improve search example
• 5e57227 perf(model): only index bulkSave errors for large batches
• ec2d92d docs(schema): clarify duplicate index warning to note index is not created (g...
• 5e98644 Merge pull request #16473 from luantaraschi/fix/clone-map-value-schematype
• Additional commits viewable in compare view

Updates mysql2 from 3.23.4 to 3.24.2

Release notes

Sourced from mysql2's releases.

v3.24.2

3.24.2 (2026-08-24)

Bug Fixes

• correct length-coded number size for the 3-byte range (#4500) (de56272)
• promise: honour trace: false on every promise-API method (#4502) (1dcd8ef), closes #4501

v3.24.1

3.24.1 (2026-08-24)

Performance Improvements

• single-pass utf8 string encoding for outgoing packets (#4495) (183e947)

v3.24.0

3.24.0 (2026-08-23)

Features

• typed parameters, and adopt integer types the server reports (#4488) (8ec20f1)

Bug Fixes

• zero dates come back as "undefined 00:00:00" with dateStrings (#4491) (5bf7bda)

Performance Improvements

• remove per-query and per-row allocation hotspots (#4486) (c86fe5a)
• serialize COM_STMT_EXECUTE in a single exact-size pass (#4494) (f3a60bc)

Changelog

Sourced from mysql2's changelog.

3.24.2 (2026-08-24)

Bug Fixes

• correct length-coded number size for the 3-byte range (#4500) (de56272)
• promise: honour trace: false on every promise-API method (#4502) (1dcd8ef), closes #4501

3.24.1 (2026-08-24)

Performance Improvements

• single-pass utf8 string encoding for outgoing packets (#4495) (183e947)

3.24.0 (2026-08-23)

Features

• typed parameters, and adopt integer types the server reports (#4488) (8ec20f1)

Bug Fixes

• zero dates come back as "undefined 00:00:00" with dateStrings (#4491) (5bf7bda)

Performance Improvements

• remove per-query and per-row allocation hotspots (#4486) (c86fe5a)
• serialize COM_STMT_EXECUTE in a single exact-size pass (#4494) (f3a60bc)

Commits

• 649e129 chore(master): release 3.24.2 (#4504)
• 87579e1 test: cover length-coded parameter sizes at the 0xFD boundary (#4503)
• 1dcd8ef fix(promise): honour trace: false on every promise-API method (#4502)
• de56272 fix: correct length-coded number size for the 3-byte range (#4500)
• ca10232 chore(master): release 3.24.1 (#4496)
• 183e947 perf: single-pass utf8 string encoding for outgoing packets (#4495)
• fabc3bc chore(master): release 3.24.0 (#4492)
• f3a60bc perf: serialize COM_STMT_EXECUTE in a single exact-size pass (#4494)
• 493f9ec ci: pin EXPLAIN to FORMAT=TRADITIONAL for MySQL 9.5+ (#4493)
• c86fe5a perf: remove per-query and per-row allocation hotspots (#4486)
• Additional commits viewable in compare view

Updates prisma from 7.9.1 to 7.10.0

Commits

• See full diff in compare view

Attestation changes

This version has no provenance attestation, while the previous version (7.9.1) was attested. Review the package versions before updating.

Updates sharedb from 6.0.1 to 6.0.2

Release notes

Sourced from sharedb's releases.

v6.0.2

• share/sharedb#718 — fix fixup transformation bug
• share/sharedb#719 — undo fixup on submit retry

Commits

• 0515287 6.0.2
• c0240c0 Merge pull request #719 from share/fix-fixup-reapplied-on-submit-retry
• 0bfe7d5 Merge pull request #718 from share/fix-fixup-transforms-wrong-pending-op
• 03c1f2d 🐛 Restore the op before fixups when retrying a submit
• 4027066 🐛 Transform every pending op by each fixup op
• c951560 Merge pull request #715 from share/dependabot/github_actions/actions/setup-no...
• 50ebd43 bump actions/setup-node from 6 to 7
• See full diff in compare view

[dd-octo-sts]

Overall package size

Self size: 8.63 MB
Deduped: 9.3 MB
No deduping: 9.3 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.4.0 | 127.33 kB | 447.04 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-official]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-01 01:13:40

Comparing candidate commit 28956d0 in PR branch dependabot/npm_and_yarn/packages/dd-trace/test/plugins/versions/databases-f02e927898 with baseline commit bf29c82 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2297 metrics, 13 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-20

• unstable max_rss_usage [-20.649MB; +33.233MB] or [-11.677%; +18.793%]

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

• unstable max_rss_usage [-7.890MB; +19.587MB] or [-3.212%; +7.974%]

scenario:dogstatsd-with-tags-20

• unstable cpu_user_time [-199.750ms; +450.579ms] or [-4.005%; +9.033%]
• unstable execution_time [-200.209ms; +452.108ms] or [-3.952%; +8.924%]
• unstable throughput [-150550.272op/s; +65204.027op/s] or [-9.089%; +3.937%]

scenario:llmobs-encode-unicode-mixed-20

• unstable max_rss_usage [-7517.458KB; +7741.458KB] or [-9.474%; +9.756%]

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

• unstable cpu_usage_percentage [-6.308%; +3.831%]

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

• unstable cpu_usage_percentage [-4.861%; +5.417%]

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

• unstable max_rss_usage [-8153.468KB; +10093.068KB] or [-5.734%; +7.098%]

scenario:plugin-pg-service-26

• unstable cpu_usage_percentage [-7.299%; +4.362%]
• unstable execution_time [-49.183ms; +98.744ms] or [-5.376%; +10.792%]
• unstable throughput [-557263.979op/s; +254868.358op/s] or [-8.381%; +3.833%]

scenario:test-optimization-large-suite-20

• unstable max_rss_usage [-4.299MB; +7.834MB] or [-5.320%; +9.694%]