search

vevcom / projectNext

Project Next is Omegas new website coming soon
MIT License
6 stars 1 forks source link

chore(deps): bump the minor group across 1 directory with 5 updates #257

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the minor group with 5 updates in the /src/prisma/prismaservice directory:

Package From To
@prisma/client 5.12.1 5.14.0
sharp 0.33.3 0.33.4
@types/node 20.12.7 20.14.0
prisma 5.12.1 5.14.0
tsc-alias 1.8.8 1.8.10

Updates @prisma/client from 5.12.1 to 5.14.0

Release notes

Sourced from @​prisma/client's releases.

5.14.0

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

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

Highlights

Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

createManyAndReturn()

We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.

Here’s an example of creating multiple posts and then immediately returning those posts.

const postBodies = req.json()['posts']

const posts = prisma.post.createManyAndReturn({
data: postBodies
});


return posts

Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.

const postBodies = req.json()['posts']

const postTitles = prisma.post.createManyAndReturn({
data: postBodies,
select: {
title: true,
},
});


return postTitles

Full documentation for this feature can be found in the Prisma Client API Reference.

Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.

MongoDB performance improvements

Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.

... (truncated)

Commits
  • e0006b1 chore(deps): update engines to 5.14.0-25.e9771e62de70f79a5e1c604a2d7c8e2a0a87...
  • 271d834 chore(deps): update engines to 5.14.0-24.879beb2a005f47f60608de797a554c8a500e...
  • d2701d4 feat: create no models flag for generate command (#24160)
  • 51ff5e4 chore(deps): update engines to 5.14.0-23.079da82321947525558fa7146f7737149538...
  • ea28e76 chore(deps): update dependency wrangler to v3.55.0 (#24147)
  • 7e66bc6 chore(deps): update engines to 5.14.0-21.6eec1600785bbff7acedfa57bc6826cdac2e...
  • 6fcc818 feat(cli): add prismaSchemaFolder support to prisma generate via `mergeSc...
  • 23aba0b docs: remove references to Prisma Slack (#24128)
  • 52589ae chore: Remove issue link from "Client did not initialize yet" (#24117)
  • c22724e feat(cli): ground work for prismaSchemaFolder, implementing validate, `form...
  • Additional commits viewable in compare view


Updates sharp from 0.33.3 to 0.33.4

Changelog

Sourced from sharp's changelog.

v0.33.4 - 16th May 2024

  • Remove experimental status from pipelineColourspace.

  • Reduce default concurrency when musl thread over-subscription detected.

  • TypeScript: add missing definitions for OverlayOptions. #4048 @​ike-gg

  • Install: add advanced option to force use of a globally-installed libvips. #4060

  • Expose bilinear resizing kernel (and interpolator). #4061

  • Ensure extend operation stays sequential for multi-page TIFF (regression in 0.32.0). #4069

  • Tighten validation of constructor text integer properties. #4071

  • Simplify internal StaySequential logic. #4074 @​kleisauke

  • Ensure negate operation occurs after profile conversion. #4096 @​adriaanmeuris

Commits
  • 19d0e27 Release v0.33.4
  • 16b764f Prerelease v0.33.4-rc.0
  • 1593ee3 Bump devDeps
  • 668b5ba Docs: changelog and credit for #4096
  • 29336f4 Ensure negate op occurs after profile conversion (#4096)
  • b5fddd7 Install: log node-addon-api version if available
  • da655a1 Reduce default concurrency for musl thread over-subscription
  • 93c615d Bump devDeps
  • f325dc3 Refactor to use C++ boolean literals rather than macros
  • 0fde71c Ensure all contributor email addresses are valid (#4088)
  • Additional commits viewable in compare view


Updates @types/node from 20.12.7 to 20.14.0

Commits


Updates prisma from 5.12.1 to 5.14.0

Release notes

Sourced from prisma's releases.

5.14.0

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

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

Highlights

Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

createManyAndReturn()

We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.

Here’s an example of creating multiple posts and then immediately returning those posts.

const postBodies = req.json()['posts']

const posts = prisma.post.createManyAndReturn({
data: postBodies
});


return posts

Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.

const postBodies = req.json()['posts']

const postTitles = prisma.post.createManyAndReturn({
data: postBodies,
select: {
title: true,
},
});


return postTitles

Full documentation for this feature can be found in the Prisma Client API Reference.

Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.

MongoDB performance improvements

Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.

... (truncated)

Commits
  • e499ef5 chore: un-iterate generate promo message (#24131)
  • d2701d4 feat: create no models flag for generate command (#24160)
  • 6fcc818 feat(cli): add prismaSchemaFolder support to prisma generate via `mergeSc...
  • 23aba0b docs: remove references to Prisma Slack (#24128)
  • c22724e feat(cli): ground work for prismaSchemaFolder, implementing validate, `form...
  • ed38a8f chore(deps): update dependency esbuild to v0.21.1 (#24110)
  • 4e72631 chore(deps): update devdependencies patch (non-major) (#24107)
  • 5163677 chore(deps): update devdependencies patch (non-major) (#24045)
  • 19a7b2e docs(cli/README): Remove Slack mention (#24015)
  • 438a718 fix: upgrade node-fetch to v3 (#24020)
  • Additional commits viewable in compare view


Updates tsc-alias from 1.8.8 to 1.8.10

Release notes

Sourced from tsc-alias's releases.

v1.8.10 (2024-05-13)

What's Changed

New Contributors

Full Changelog: https://github.com/justkey007/tsc-alias/compare/v1.8.9...v1.8.10

v1.8.9 (2024-05-09)

What's Changed

New Contributors

Full Changelog: https://github.com/justkey007/tsc-alias/compare/v1.8.8...v1.8.9

Commits


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions