chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@commitlint/cli (source)	18.4.4 -> 18.6.1					devDependencies	minor
@commitlint/config-conventional (source)	18.4.4 -> 18.6.3					devDependencies	minor
@killbasa/redis-utils	^0.0.9 -> ^0.0.10					dependencies	patch
@prisma/client (source)	5.8.0 -> 5.13.0					dependencies	minor
@sapphire/decorators (source)	6.0.3 -> 6.1.0					dependencies	minor
@sapphire/discord.js-utilities (source)	7.1.5 -> 7.2.1					dependencies	minor
@sapphire/duration (source)	1.1.1 -> 1.1.2					dependencies	patch
@sapphire/fetch (source)	3.0.1 -> 3.0.2					dependencies	patch
@sapphire/framework (source)	5.0.6 -> 5.2.1					dependencies	minor
@sapphire/plugin-api (source)	6.1.0 -> 6.1.1					dependencies	patch
@sapphire/plugin-logger (source)	4.0.1 -> 4.0.2					dependencies	patch
@sapphire/plugin-scheduled-tasks (source)	10.0.0 -> 10.0.1					dependencies	patch
@sapphire/utilities (source)	3.15.2 -> 3.15.3					dependencies	patch
@sentry/integrations (source)	7.93.0 -> 7.114.0					dependencies	minor
@sentry/node (source)	7.93.0 -> 7.114.0					dependencies	minor
@sentry/types (source)	7.93.0 -> 7.114.0					devDependencies	minor
@swc/core (source)	1.3.102 -> 1.5.5					devDependencies	minor
@types/node (source)	20.11.0 -> 20.12.11					devDependencies	minor
@typescript-eslint/eslint-plugin (source)	6.18.1 -> 6.21.0					devDependencies	minor
@typescript-eslint/parser (source)	6.18.1 -> 6.21.0					devDependencies	minor
@vitest/coverage-v8 (source)	1.2.0 -> 1.6.0					devDependencies	minor
@vitest/ui (source)	1.2.0 -> 1.6.0					devDependencies	minor
discord.js (source)	14.14.1 -> 14.15.2					dependencies	minor
docker/build-push-action	v5.1.0 -> v5.3.0					action	minor
docker/login-action	v3.0.0 -> v3.1.0					action	minor
docker/setup-buildx-action	v3.0.0 -> v3.3.0					action	minor
dotenv	16.3.1 -> 16.4.5					dependencies	minor
eslint (source)	8.56.0 -> 8.57.0					devDependencies	minor
eslint-config-turbo (source)	1.11.3 -> 1.13.3					devDependencies	minor
humanize-duration	3.31.0 -> 3.32.0					dependencies	minor
ioredis	5.3.2 -> 5.4.1					dependencies	minor
lint-staged	15.2.0 -> 15.2.2					devDependencies	patch
meilisearch	^0.36.0 -> ^0.39.0					dependencies	minor
node	20.11.0-alpine3.19 -> 20.13.1-alpine3.19					final	minor
node	20.11.0-alpine3.19 -> 20.13.1-alpine3.19					stage	minor
prettier (source)	3.2.1 -> 3.2.5					devDependencies	patch
prisma (source)	5.8.0 -> 5.13.0					devDependencies	minor
prom-client	15.1.0 -> 15.1.2					dependencies	patch
schemix	1.14.1 -> 1.15.0					devDependencies	minor
tsup (source)	8.0.1 -> 8.0.2					devDependencies	patch
turbo (source)	1.11.3 -> 1.13.3					devDependencies	minor
typescript (source)	5.3.3 -> 5.4.5					devDependencies	minor
utf-8-validate	6.0.3 -> 6.0.4					dependencies	patch
vite-tsconfig-paths	4.2.3 -> 4.3.2					devDependencies	minor
vitepress (source)	1.0.0-rc.36 -> 1.1.4					devDependencies	minor
vitest (source)	1.2.0 -> 1.6.0					devDependencies	minor
yarn (source)	4.0.2 -> 4.2.2					packageManager	minor

---

Release Notes

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

v18.6.1

Compare Source

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

v18.6.0

Compare Source

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

v18.5.0

Compare Source

Features

• cli: print-config now can be configured to print a json in stdout (#​3863) (6381a2d), closes #​3819

18.4.4 (2024-01-04)

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

18.4.3 (2023-11-21)

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

18.4.2 (2023-11-16)

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

18.4.1 (2023-11-12)

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

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

v18.6.3

Compare Source

Bug Fixes

• fix: add missing entry wrapper.mjs by @​JounQin in https://github.com/conventional-changelog/commitlint/pull/3966

Full Changelog: conventional-changelog/commitlint@v18.6.2...v18.6.3

v18.6.2

Compare Source

Bug Fixes

• config-conventional: use default export (#​3911) (bc48408)

v18.6.1

Compare Source

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

v18.6.0

Compare Source

Features

• rules: add header-trim rule (#​3199) (#​3871) (331579a)

v18.5.0

Compare Source

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

18.4.4 (2024-01-04)

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

18.4.3 (2023-11-21)

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

18.4.2 (2023-11-16)

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

killbasa/redis-utils (@​killbasa/redis-utils)

v0.0.10

Compare Source

prisma/prisma (@​prisma/client)

v5.13.0

Compare Source

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

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

Highlights

omit fields from Prisma Client queries (Preview)

We’re excited to announce Preview support for the omit option within the Prisma Client query options. The highly-requested omit feature now allows you to exclude fields that you don’t want to retrieve from the database on a per-query basis.

By default, when a query returns records, the result includes all scalar fields of the models defined in the Prisma schema. select can be used to return specific fields, while omit can now be used to exclude specific fields. omit lives at the same API level and works on all of the same Prisma Client model queries as select. Note, however, that omit and select are mutually exclusive. In other words, you can’t use both in the same query.

To get started using omit, enable the omitApi Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["omitApi"]
}

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

Here is an example of using omit:

// Includes all fields except password
await prisma.user.findMany({
  omit: {
   password: true
  },
})

Here is an example of using omit with include:

// Includes all user fields except user's password and title of user's posts
await prisma.user.findMany({
  omit: {
   password: true
  },
  include: {
    posts: {
      omit: {
        title: true
      },
    },
  },
})

Expand to view the example Prisma schema

model User {
  id       Int     @​id @​default(autoincrement())
  email    String  @​unique
  name     String?
  password String
  posts    Post[]
}

model Post {
  id       Int    @​id @​default(autoincrement())
  title    String
  author   User   @​relation(fields: [authorId], references: [id])
  authorId Int
}

Many users have requested a global implementation of omit. This request will be accommodated in the future. In the meantime, you can follow the issue here.

📣 Share your feedback: omitApi Preview feature

📚 Documentation: omit - Prisma Client API Reference

Fixes and improvements

Prisma Migrate

• Nicer Datamodel Type validation

Prisma Client

• ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using Powershell)

Credits

Huge thanks to @​ospfranco, @​pranayat, @​yubrot, @​skyzh, @​anuraaga, @​yehonatanz, @​arthurfiorette, @​elithrar, @​tockn, @​Kuhave, @​obiwac for helping!

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://togithub.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: 'sonali@prisma.io' },
    { name: 'Alex', email: 'alex@prisma.io' },
    { name: 'Yewande', email: 'yewande@prisma.io' },
    { name: 'Angelina', email: 'angelina@prisma.io' },
  ],
})

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 datab

---

Configuration

📅 Schedule: Branch creation - "before 10am on Saturday" (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.