Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade: , , , #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade: , , , #20

wants to merge 1 commit into from
+21 −20

Conversation

Cabreira97
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯‍♂ The following dependencies are linked and will therefore be updated together.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name Versions Released on

@nestjs/common
from 10.3.10 to 10.4.1 | 2 versions ahead of your current version | 25 days ago
on 2024-08-13
@nestjs/core
from 10.3.10 to 10.4.1 | 2 versions ahead of your current version | 25 days ago
on 2024-08-13
@nestjs/platform-express
from 10.3.10 to 10.4.1 | 2 versions ahead of your current version | 25 days ago
on 2024-08-13
@prisma/client
from 5.17.0 to 5.18.0 | 45 versions ahead of your current version | a month ago
on 2024-08-06

Release notes
Package name: @nestjs/common from @nestjs/common GitHub release notes
Package name: @nestjs/core from @nestjs/core GitHub release notes
Package name: @nestjs/platform-express from @nestjs/platform-express GitHub release notes
Package name: @prisma/client
  • 5.18.0 - 2024-08-06

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

    Highlights

    Native support for UUIDv7

    Previous to this release, the Prisma Schema function uuid() did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.

    UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!

    To support this, we’ve updated the uuid() function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are 4 and 7, with 4 being the default.

    model User {
    id String @id @default(uuid()) // defaults to 4
    name String
    }

    model User {
    id String @id @default(uuid(4)) // same as above, but explicit
    name String
    }

    model User {
    id String @id @default(uuid(7)) // will use UUIDv7 instead of UUIDv4
    name String
    }

    Bug squashing

    We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:

    Fixes and improvements

    Prisma

    Language tools (e.g. VS Code)

    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 🙏

    Credits

    Huge thanks to @ mcuelenaere, @ pagewang0, @ Druue, @ key-moon, @ Jolg42, @ pranayat, @ ospfranco, @ yubrot, @ skyzh, @ haaawk for helping!

  • 5.18.0-integration-revert-24949-fix-ts-version.1 - 2024-08-06
  • 5.18.0-integration-fix-config-dir-client.5 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.4 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.3 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.2 - 2024-07-17
  • 5.18.0-integration-fix-config-dir-client.1 - 2024-07-17
  • 5.18.0-integration-feat-typed-sql.9 - 2024-08-05
  • 5.18.0-integration-feat-typed-sql.8 - 2024-08-05
  • 5.18.0-integration-feat-typed-sql.7 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.6 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.5 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.4 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.3 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.2 - 2024-07-29
  • 5.18.0-integration-feat-typed-sql.1 - 2024-07-29
  • 5.18.0-integration-engines-5-18-0-9-feat-gh-actions-0b3765edade679247b3c9856bcabbcdc1736853e.1 - 2024-07-19
  • 5.18.0-integration-engines-5-18-0-7-feat-gh-actions-462cf67beffd0cc97802a8034d58a38ec9c58b99.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-6-feat-gh-actions-19bafc70f9e564e8f5792bd8a9cd4bad4df5748e.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-5-feat-gh-actions-5f2a1d1133b515a5b4cbf1b17ef011a9fe22b559.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-4-feat-gh-actions-db4307dd3283e239e498436ea27707d22af180f3.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-3-feat-gh-actions-3d6f612a21393259032d9b8630f4b621b4f3c32f.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-26-feat-introspect-sql-4dcdf8b8304815e12f4af0e41837efb42c98e9b7.1 - 2024-08-02
  • 5.18.0-integration-engines-5-18-0-24-integration-fix-d1-int64-46841fc537adb365fc503b23779c98a19ac9835d.2 - 2024-07-31
  • 5.18.0-integration-engines-5-18-0-24-integration-fix-d1-int64-46841fc537adb365fc503b23779c98a19ac9835d.1 - 2024-07-31
  • 5.18.0-integration-engines-5-18-0-20-feat-introspect-sql-b2b600c154792b1859dfb09b93d383681a1b2bf0.1 - 2024-07-29
  • 5.18.0-integration-engines-5-18-0-2-feat-gh-actions-5ed0cbc35ff1fdd02f7d09f7819a213f9b5e6b9f.1 - 2024-07-16
  • 5.18.0-integration-engines-5-18-0-14-integration-test-gh-branch-555baf1ea1fca8f73cebed665b226cf3b8c4798b.2 - 2024-07-22
  • 5.18.0-integration-engines-5-18-0-14-integration-test-gh-branch-555baf1ea1fca8f73cebed665b226cf3b8c4798b.1 - 2024-07-22
  • 5.18.0-integration-engines-5-18-0-12-improve-quaint-column-type-331a7dd91f2553e6a77b58649b55472bca4fa225.1 - 2024-07-22
  • 5.18.0-integration-engines-5-17-0-4-feat-remove-actors-attempt-2-e7f608ab076eda9e1264e600ce3a140f0bc06bbe.1 - 2024-07-31
  • 5.18.0-dev.14 - 2024-08-06
  • 5.18.0-dev.13 - 2024-08-05
  • 5.18.0-dev.12 - 2024-08-05
  • 5.18.0-dev.11 - 2024-08-02
  • 5.18.0-dev.10 - 2024-07-24
  • 5.18.0-dev.9 - 2024-07-24
  • 5.18.0-dev.8 - 2024-07-23
  • 5.18.0-dev.7 - 2024-07-23
  • 5.18.0-dev.6 - 2024-07-22
  • 5.18.0-dev.5 - 2024-07-22
  • 5.18.0-dev.4 - 2024-07-22
  • 5.18.0-dev.3 - 2024-07-22
  • 5.18.0-dev.2 - 2024-07-19
  • 5.18.0-dev.1 - 2024-07-17
  • 5.17.0 - 2024-07-16

    🌟 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

    references

    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.

    image

    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.

    image (1)

    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

    Prisma

    Language tools (e.g. VS Code)

    Credits

    Huge thanks to @ key-moon, @ pranayat, @ yubrot, @ skyzh for helping!

from @prisma/client GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade multiple dependencies with Snyk
f4bd750 
Snyk has created this PR to upgrade:
  - @nestjs/common from 10.3.10 to 10.4.1.
    See this package in npm: https://www.npmjs.com/package/@nestjs/common
  - @nestjs/core from 10.3.10 to 10.4.1.
    See this package in npm: https://www.npmjs.com/package/@nestjs/core
  - @nestjs/platform-express from 10.3.10 to 10.4.1.
    See this package in npm: https://www.npmjs.com/package/@nestjs/platform-express
  - @prisma/client from 5.17.0 to 5.18.0.
    See this package in npm: https://www.npmjs.com/package/@prisma/client

See this project in Snyk:
https://app.snyk.io/org/cabreira97/project/20bcda88-de7e-44d6-819e-6eea56f2ae36?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Cabreira97 @snyk-bot