fix(deps): 🐛 🔗 update all dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update	Pending
@apollo/server (source)	4.10.0 -> 4.10.2					dependencies	patch
@aws-sdk/client-cloudformation (source)	3.526.0 -> 3.552.0					dependencies	minor	3.555.0 (+1)
@aws-sdk/client-lambda (source)	3.525.0 -> 3.552.0					dependencies	minor	3.554.0
@commitlint/cli (source)	19.0.3 -> 19.2.1					dependencies	minor
@commitlint/config-conventional (source)	19.0.3 -> 19.1.0					dependencies	minor
@graphql-tools/utils (source)	10.1.0 -> 10.1.2					dependencies	patch
@prisma/client (source)	5.10.2 -> 5.12.1					dependencies	minor
@smithy/util-waiter (source)	2.1.3 -> 2.2.0					dependencies	minor
@tsconfig/docusaurus (source)	2.0.2 -> 2.0.3					devDependencies	patch
@tsconfig/node20 (source)	20.1.2 -> 20.1.4					dependencies	patch
@types/aws-lambda (source)	8.10.135 -> 8.10.137					devDependencies	patch
@types/node (source)	20.11.24 -> 20.12.7					devDependencies	minor
@types/node (source)	20.11.24 -> 20.12.7					dependencies	minor
@typescript-eslint/eslint-plugin (source)	7.1.1 -> 7.6.0					dependencies	minor
@typescript-eslint/parser (source)	7.1.1 -> 7.6.0					dependencies	minor
actions/cache	ab5e6d0 -> 0c45773					action	digest
aws-cdk (source)	2.131.0 -> 2.137.0					devDependencies	minor
aws-cdk-lib (source)	2.131.0 -> 2.137.0					dependencies	minor
dotenv-cli	7.3.0 -> 7.4.1					devDependencies	minor
esbuild	0.20.1 -> 0.20.2					devDependencies	patch
eslint (source)	8.57.0 -> 9.0.0					dependencies	major
pnpm (source)	8.15.4 -> 8.15.6					packageManager	patch	8.15.7
prettier-plugin-packagejson	2.4.12 -> 2.4.14					dependencies	patch	2.5.0
prisma (source)	5.10.2 -> 5.12.1					devDependencies	minor
tsx	4.7.1 -> 4.7.2					devDependencies	patch
turbo (source)	1.12.4 -> 1.13.2					dependencies	minor
typescript (source)	5.3.3 -> 5.4.5					dependencies	minor
typescript (source)	5.3.3 -> 5.4.5					devDependencies	minor
unconfig	0.3.11 -> 0.3.12					dependencies	patch	0.3.13
winston	3.12.0 -> 3.13.0					dependencies	minor

---

Release Notes

apollographql/apollo-server (@​apollo/server)

v4.10.2

Compare Source

Patch Changes

• #​7849 c7e514c Thanks @​TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

v4.10.1

Compare Source

Patch Changes

• #​7843 72f568e Thanks @​bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.

aws/aws-sdk-js-v3 (@​aws-sdk/client-cloudformation)

v3.552.0

Compare Source

3.552.0(2024-04-09)

Chores

• lib-dynamodb: re-export options and NativeAttribute* types (#​5982) (4de64333)
• codegen sync for smithy-typescript 0.20.1 (#​5980) (d201a43a)

Documentation Changes

• fix typos (#​5972) (8493608e)

New Features

• clients: update client endpoints as of 2024-04-09 (30faa2cf)
• client-codebuild: Add new webhook filter types for GitHub webhooks (e78df26c)
• client-rds: This release adds support for specifying the CA certificate to use for the new db instance when restoring from db snapshot, restoring from s3, restoring to point in time, and creating a db instance read replica. (59e2f13f)
• client-pinpoint: The OrchestrationSendingRoleArn has been added to the email channel and is used to send emails from campaigns or journeys. (18bbe71a)
• client-mediaconvert: This release includes support for bringing your own fonts to use for burn-in or DVB-Sub captioning workflows. (b1fb0ed4)

---

For list of updated packages, view updated-packages.md in assets-3.552.0.zip

v3.549.0

Compare Source

3.549.0(2024-04-04)

Chores

• codegen: update Smithy to 1.47.0 (#​5956) (c3498251)

New Features

• clients: update client endpoints as of 2024-04-04 (da490a15)
• client-ivs: API update to include an SRT ingest endpoint and passphrase for all channels. (9d148371)
• client-cleanrooms: Feature: New schemaStatusDetails field to the existing Schema object that displays a status on Schema API responses to show whether a schema is queryable or not. New BatchGetSchemaAnalysisRule API to retrieve multiple schemaAnalysisRules using a single API call. (30e75ea7)
• client-emr-containers: This release adds support for integration with EKS AccessEntry APIs to enable automatic Cluster Access for EMR on EKS. (36c67508)
• client-ec2: Amazon EC2 G6 instances powered by NVIDIA L4 Tensor Core GPUs can be used for a wide range of graphics-intensive and machine learning use cases. Gr6 instances also feature NVIDIA L4 GPUs and can be used for graphics workloads with higher memory requirements. (379b756b)
• client-b2bi: Adding support for X12 5010 HIPAA EDI version and associated transaction sets. (f4cb659c)
• client-verifiedpermissions: Adds GroupConfiguration field to Identity Source API's (d2d80fda)

---

For list of updated packages, view updated-packages.md in assets-3.549.0.zip

v3.548.0

Compare Source

Features

• client-cloudformation: This release would return a new field - PolicyAction in cloudformation's existed DescribeChangeSetResponse, showing actions we are going to apply on the physical resource (e.g., Delete, Retain) according to the user's template (98e1d9f)

v3.540.0

Compare Source

Bug Fixes

• util-endpoints: augment endpointFunctions inline in endpointResolver functions (#​5933) (42a791d)

v3.537.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.536.0

Compare Source

Features

• client-cloudformation: This release supports for a new API ListStackSetAutoDeploymentTargets, which provider auto-deployment configuration as a describable resource. Customers can now view the specific combinations of regions and OUs that are being auto-deployed. (29679ab)

v3.535.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.533.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.532.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

3.529.1 (2024-03-08)

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.529.1

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.529.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

aws/aws-sdk-js-v3 (@​aws-sdk/client-lambda)

v3.552.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.549.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.548.0

Compare Source

Features

• client-lambda: Add Ruby 3.3 (ruby3.3) support to AWS Lambda (66721f6)

v3.540.0

Compare Source

Bug Fixes

• util-endpoints: augment endpointFunctions inline in endpointResolver functions (#​5933) (42a791d)

v3.536.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.535.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.533.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

3.529.1 (2024-03-08)

Note: Version bump only for package @​aws-sdk/client-lambda

v3.529.1

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.529.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

conventional-changelog/commitlint (@​commitlint/cli)

v19.2.1

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.2.0

Compare Source

Features

• cli: introduce new --last flag, to stop recommending HEAD~1 (#​3916) (99f4f3f)

v19.1.0

Compare Source

Note: Version bump only for package @​commitlint/cli

19.0.3 (2024-02-28)

Note: Version bump only for package @​commitlint/cli

19.0.2 (2024-02-28)

Note: Version bump only for package @​commitlint/cli

19.0.1 (2024-02-27)

Bug Fixes

• drop resolve-from, resolve-global and import-fresh, resolve global packages correctly (#​3939) (8793c63), closes #​3938

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.1.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

19.0.3 (2024-02-28)

Note: Version bump only for package @​commitlint/config-conventional

ardatan/graphql-tools (@​graphql-tools/utils)

v10.1.2

Compare Source

Patch Changes

• fff2399 Thanks @​ardatan! - Respect toJSON in astFromValueUntyped

v10.1.1

Compare Source

Patch Changes

• #​5931 baf3c28 Thanks @​henryqdineen! - fix filterSchema argument filter for schema with non-default root types

prisma/prisma (@​prisma/client)

v5.12.1

Compare Source

Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for migrate diff and db pull

The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

New option for migrate diff: -o or --output

We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

Related issues:

• ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #​23702
• [prisma migrate resolve --applied not working on new project, migration ... could not be found.][https://github.com/prisma/prisma/issues/17558](https://github.com/prisma/prisma/issues/17558)8)

v5.12.0

Compare Source

Today, we are excited to share the 5.12.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release.

Highlights

Cloudflare D1 (Preview)

This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳

D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.

When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.

To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.

Here is an example of sending a query to your D1 database using Prisma Client in your Worker:

// src/index.ts file
import { PrismaClient } from '@​prisma/client'
import { PrismaD1 } from '@​prisma/adapter-d1'

// Add the D1Database to the Env interface
export interface Env {
// This must match the binding name defined in your wrangler.toml configuration
  DB: D1Database
}

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    // Make sure the database name matches the binding name in wrangler.toml and Env interface
    const adapter = new PrismaD1(env.DB)
    // Instantiate PrismaClient using the PrismaD1 driver adapter
    const prisma = new PrismaClient({ adapter })

    const users = await prisma.user.findMany()
    const result = JSON.stringify(users)
    return new Response(result)
  },
}

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

✍️ Blog post: Build Applications at the Edge with Prisma ORM & Cloudflare D1 (Preview)

📣 Share your feedback: D1 Driver Adapter

🚀 Example project: Deploy a Cloudflare Worker with D1

createMany() for SQLite

Bringing support for createMany() in SQLite has been a long-awaited and highly requested feature ⭐

createMany() is a method on Prisma Client, released back in version 2.16.0, that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data.

Here is an example of using createMany() to create new users:

const users = await prisma.user.createMany({
  data: [
    { name: 'Sonali', email: '[email protected]' },
    { name: 'Alex', email: '[email protected]' },
    { name: 'Yewande', email: '[email protected]' },
    { name: 'Angelina', email: '[email protected]' },
  ],
})

Before this release, if you wanted to perform bulk inserts with SQLite, you would have most likely used $queryRawUnsafe to execute raw SQL queries. But now you don’t have to go through all that trouble 🙂

With SQLite, createMany() works exactly the same way from an API standpoint as it does with other databases except it does not support the skipDuplicates option. At the behavior level, SQLite will split createMany() entries into multiple INSERT queries when the model in your schema contains fields with attributes like @default(dbgenerated()) or @default(autoincrement()) and when the fields are not consistently provided with values across the entries.

📚Documentation: createMany() - Prisma Client API Reference

Fixes and Improvements

Prisma Client

• N+1 Issue with Decimal data type and combining queries (batching)
• Batched findUnique() error out when the field is of Boolean type
• relationJoins MySQL converts nested Decimal to float
• Unexpected query leading to querying full table when using batched findUnique()
• node-postgres (pg) errors with misleading P2010 PrismaClientKnownRequestError when using @prisma/adapter-pg with SSL (?sslmode=require)
• D1 DateTime type does not work

Credits

Huge thanks to @​yubrot, @​skyzh, @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​arthurfiorette, @​elithrar for helping!

v5.11.0

Compare Source

Today, we are excited to share the 5.11.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

• Vercel Edge Functions and Vercel Edge Middleware
• Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

• Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
• PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
• pg driver (for traditional PostgreSQL databases)
• @libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

Performance improvements in nested create operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

Prisma Client

• Prisma errors when not using the major.minor.patch versioning system
• mongodb where condition resulted in combined $ne but should not be $eq
• Node hangs when console.log(new PrismaClient())
• Add wolfy linux to supported OS
• Support Linux Gentoo
• Know engines to download for Void Linux
• Engine does not support Linux distro "openeuler"
• Prisma Doesn't Recognize Crystal Linux distro
• Regression: Mapped enum throws error (collation cp1250_czech_cs or similar)
• NOT condition leaks out of its desired bounds
• The column does not exist in the current database.
• Logging PrismaClient object is slow
• Running prisma generate on Litespeed Web Server cPanel with ssh
• Prisma doesn't know which engines to download for the Linux distro "guttaos"
• Error in driver-adapter-utils with tsc: Cannot find namespace 'debug'.
• VS Code debugger freeze from time to time, when Prisma Client is involved
• push method still unimplemented for scalar lists in CockroachDB
• Invalid character error persists on 5.10.1 in Prisma Studio
• Add "Peppermint OS" to list of supported distros
• runtimeDescription is not defined error

Prisma Migrate

• Prisma with UOS or Deepin
• Warning: Linux distro "slackware"
• Error when run npx prisma db pull with DeepinOS 20.9GNU/LInux
• Add solus to list of known supported distros
• NixOS not recognised as a Linux distribution
• Prisma Warning on Ubuntu 20.04
• Let Prisma detect Artix Linux distro
• couldn't identify clear-linux-os
• Prisma doesn't know which engines to download with Linux Mint
• Error: Invalid character when schema.prisma includes Chinese/Non-ASCII characters in a comment

Prisma Engines

• [DA] Planetscale engine tests: aggregations
• [DA] Planetscale engine tests: json filtering
• [DA] Planetscale engine tests: order and pagination
• [DA] Planetscale engine tests: oids
• [DA] Planetscale engine tests: nested_createmany_fail_dups
• [DA] Planetscale engine tests: create_many_error_dups
• [DA] Planetscale engine tests: upsert_fails_if_filter_dont_match

awslabs/smithy-typescript (@​smithy/util-waiter)

v2.2.0

Compare Source

Minor Changes

• 38f9a61: Update package dependencies

Patch Changes

• Updated dependencies [38f9a61]
• Updated dependencies [661f1d6]
  • @​smithy/abort-controller@​2.2.0
  • @​smithy/types@​2.12.0

v2.1.4

Compare Source

Patch Changes

• Updated dependencies [43f3e1e]
  • [@​smithy/types](h

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.