Bump the prisma group across 1 directory with 2 updates

[dependabot]

Bumps the prisma group with 2 updates in the / directory: @prisma/client and prisma.

Updates @prisma/client from 5.13.0 to 5.17.0

Release notes

Sourced from @​prisma/client's releases.

5.17.0

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

VSCode extension improvements

We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

Find references across schema files

The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

Added context on hover

When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

Additional quick fixes

We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

QueryRaw performance improvements

We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

Fixes and improvements

Prisma Client

• Remove or change This is the 10th instance of Prisma Client being started. Make sure this is intentional. warning

Prisma

• Prisma generate option --allow-no-models doesn't work.

Language tools (e.g. VS Code)

• LSP Rename incorrectly maps field name and appends character

... (truncated)

Commits

• 8144267 chore(deps): update engines to 5.17.0-31.393aa359c9ad4a4bb28630fb5613f9c281cd...
• 2045892 chore(deps): update engines to 5.17.0-30.9721e9ba461e8bae3b4bb2acac96d8d80ef0...
• 3c27a5d chore(deps): update engines to 5.17.0-29.d0037d055708c381097816f5847147d55bc3...
• 7da6f03 feat: support new queryRaw result format (#24783)
• f739ec2 fix(client): Fix globalOmit with methods that do not return the model (#24765)
• 6cabc4e feat(generator-helper): add typings for indexes in DMMF (#24762)
• cbd23a2 chore(deps): update engines to 5.17.0-8.5954db1fa6f2b12aeb1d5cf503b870c3bb6f8...
• 536f22c chore(deps): update engines to 5.17.0-7.4b84e51743fad4e1b5bcbf8779aa03568f755...
• 1cc5cb0 fix(cli): restored prisma generate --allow-no-models after regression (#24741)
• 1867b68 chore(deps): update devdependencies patch (non-major) (#24639)
• Additional commits viewable in compare view

Updates prisma from 5.13.0 to 5.17.0

Release notes

Sourced from prisma's releases.

5.17.0

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

VSCode extension improvements

We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

Find references across schema files

The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

Added context on hover

When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

Additional quick fixes

We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

QueryRaw performance improvements

We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

Fixes and improvements

Prisma Client

• Remove or change This is the 10th instance of Prisma Client being started. Make sure this is intentional. warning

Prisma

• Prisma generate option --allow-no-models doesn't work.

Language tools (e.g. VS Code)

• LSP Rename incorrectly maps field name and appends character

... (truncated)

Commits

• a15d3b9 feat(cli, generate command): Added promo array to rotate and make cli messagi...
• 7308378 feat(cli): Support prisma platform auth show --sensitive (#24745)
• 190bac1 chore(cli): cleanup import message when running generate (#24739)
• 1cc5cb0 fix(cli): restored prisma generate --allow-no-models after regression (#24741)
• 1867b68 chore(deps): update devdependencies patch (non-major) (#24639)
• f147dbe feat(cli): Add format --check (#24613)
• 37adb2d chore: set minimum compilation target to ES2021 (>= Node.js 16.4.x) (#24646)
• e661724 chore(deps): update dependency esbuild to v0.23.0 (#24693)
• 61c901b feat(cli): use new login endpoint for optimize (#24570)
• 13172c2 feat(prismaSchemaFolder): Resolve paths in datasource blocks relative to the ...
• 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 no longer updatable, so this is no longer needed.