deps: bump the all-dependencies group across 1 directory with 5 updates

[dependabot]

Bumps the all-dependencies group with 5 updates in the / directory:

Package	From	To
@prisma/client	6.16.3	6.18.0
cache-manager	7.2.3	7.2.4
cacheable	2.0.3	2.1.1
prisma	6.16.3	6.18.0
rimraf	6.0.1	6.1.0

Updates @prisma/client from 6.16.3 to 6.18.0

Release notes

Sourced from @​prisma/client's releases.

6.18.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

• prisma init now creates a prisma.config.ts automatically

When creating a new project with 6.18.0, prisma init will now create a prisma.config.ts file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the schema.prisma file are now able to be set in the prisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.

• Support for defining your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic" , which will be required for Prisma v7

import { defineConfig, env } from "prisma/config";
export default defineConfig({
    // The Rust-compiled schema engine 
    engine: "classic",
    datasource: {
        url: env('DATABASE_URL'),
    }
});

• prisma/prisma#28291 Support multiple Prisma instances with different providers
• prisma/prisma#28305 Add env helper function
• prisma/prisma#28266 Add support for js or classic as engine types in prisma.config
• prisma/prisma#28139 Map Bytes to Uint8Array depending on Typescript version

Preparing for Prisma v7

While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to prisma.config.ts will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

Database Metric in Console

Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:

• Total egress
• Average response size
• Average query duration

In addition, you can also get insights into how to improve your query caching and gain better performance.

... (truncated)

Commits

• 1bd7fd2 fix(tests): don't replace the process.env object (#28331)
• 7633148 chore(deps): update engines to 6.18.0-8.34b5a692b7bd79939a9a2c3ef97d816e749cd...
• 4078626 chore: fix jest inline snapshot update (#28330)
• 50f6514 fix: support multiple Prisma instances with different providers (#28291)
• 3bc04bc chore(deps): update engines to 6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39cc...
• 6c5a217 fix(adapter-pg): historical dates (#28212)
• 30bdd63 chore(deps): update engines to 6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7...
• 1341489 chore(deps): update engines to 6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0...
• c524934 chore: upgrade OpenTelemetry deps and refresh tracing setup in client (#28268)
• 423b585 fix: revert "chore: use pnpm catalog (#28236)" (#28271)
• Additional commits viewable in compare view

Updates cache-manager from 7.2.3 to 7.2.4

Commits

• See full diff in compare view

Updates cacheable from 2.0.3 to 2.1.1

Commits

• See full diff in compare view

Updates prisma from 6.16.3 to 6.18.0

Release notes

Sourced from prisma's releases.

6.18.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

• prisma init now creates a prisma.config.ts automatically

When creating a new project with 6.18.0, prisma init will now create a prisma.config.ts file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the schema.prisma file are now able to be set in the prisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.

• Support for defining your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic" , which will be required for Prisma v7

import { defineConfig, env } from "prisma/config";
export default defineConfig({
    // The Rust-compiled schema engine 
    engine: "classic",
    datasource: {
        url: env('DATABASE_URL'),
    }
});

• prisma/prisma#28291 Support multiple Prisma instances with different providers
• prisma/prisma#28305 Add env helper function
• prisma/prisma#28266 Add support for js or classic as engine types in prisma.config
• prisma/prisma#28139 Map Bytes to Uint8Array depending on Typescript version

Preparing for Prisma v7

While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to prisma.config.ts will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

Database Metric in Console

Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:

• Total egress
• Average response size
• Average query duration

In addition, you can also get insights into how to improve your query caching and gain better performance.

... (truncated)

Commits

• 7463164 feat(config): env utility improvements (#28332)
• 1bd7fd2 fix(tests): don't replace the process.env object (#28331)
• 4078626 chore: fix jest inline snapshot update (#28330)
• a3e36ae feat(config): add support for engine?: 'js' | 'classic' (#28266)
• 6960355 feat: support OpenTelemetry in loadable sub-commands (#28272)
• 423b585 fix: revert "chore: use pnpm catalog (#28236)" (#28271)
• 10fab6b chore: use pnpm catalog (#28236)
• 58e44ee chore: cli - remove unused/unnecessary dependencies (#28081)
• c5ff908 chore: bump get-port to 7.1.0 (#28080)
• See full diff in compare view

Updates rimraf from 6.0.1 to 6.1.0

Changelog

Sourced from rimraf's changelog.

6.1

• Move to native fs/promises usage instead of promisifying manually.

6.0

• Drop support for nodes before v20
• Add --version to CLI

5.0

• No default export, only named exports

4.4

• Provide Dirent or Stats object as second argument to filter

4.3

• Return boolean indicating whether the path was fully removed
• Add filter option
• bin: add --verbose, -v to print files as they are deleted
• bin: add --no-verbose, -V to not print files as they are deleted
• bin: add -i --interactive to be prompted on each deletion
• bin: add -I --no-interactive to not be prompted on each deletion
• 4.3.1 Fixed inappropriately following symbolic links to directories

v4.2

• Brought back glob support, using the new and improved glob v9

v4.1

• Improved hybrid module with no need to look at the .default dangly bit. .default preserved as a reference to rimraf for compatibility with anyone who came to rely on it in v4.0.
• Accept and ignore -rf and -fr arguments to the bin.

v4.0

• Remove glob dependency entirely. This library now only accepts actual file and folder names to delete.
• Accept array of paths or single path.
• Windows performance and reliability improved.
• All strategies separated into explicitly exported methods.
• Drop support for Node.js below version 14
• rewrite in TypeScript

... (truncated)

Commits

• 18dc77a 6.1.0
• 2bd2e62 changelog 6.1
• 19311cf refactor: switch to native fs.promises
• 0c437d4 Create separate dir for integration tests
• 65a3b8a Do not pass unnecessary rest args to fs functions
• 02b31b7 Use the same ignoreENOENT and fixEPERM utils everywhere
• c012f4f Mock process.platform with t.intercept
• c72278a Use tap.intercept to test bin
• 549d1e8 Configure tap coverage-map
• a76970b benchmark: add options to filter and compare benchmarks
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.