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

chore(deps): update all non-major dependencies #355

Merged
merged 1 commit into from
Jun 25, 2023
Merged

chore(deps): update all non-major dependencies #355

merged 1 commit into from
Jun 25, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 25, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@next/font 13.4.6 -> 13.4.7 age adoption passing confidence
@prisma/client (source) ^4.15.0 -> ^4.16.1 age adoption passing confidence
framer-motion ^10.12.16 -> ^10.12.17 age adoption passing confidence
next (source) ^13.4.6 -> ^13.4.7 age adoption passing confidence
next-seo ^6.0.0 -> ^6.1.0 age adoption passing confidence
swr (source) ^2.1.5 -> ^2.2.0 age adoption passing confidence

Release Notes

vercel/next.js

v13.4.7

Compare Source

Core Changes
  • Route Module Updates Redux: #​51373
  • Lock down server IPC address: #​51378
  • Revert "Route Module Updates Redux": #​51409
  • Fix bundling of Server Actions: #​51367
  • Fix pnpm lock: #​51503
  • router: add layout and other file supports to parallel routes: #​51413
  • Next Build Turbo POC: #​49942
  • add edge rendering for app dir for Turbopack: #​50830
  • Fix shared action module in two layers: #​51510
  • Revert "Next Build Turbo POC (#​49942)": #​51538
  • Fix font styles on react dev overlay: #​51518
  • fix typo in x-next-revalidate-tag-token header: #​51432
  • Add docs links to RSC errors: #​51557
  • Moved new line to warnOnce call: #​51552
  • Update id env prefix: #​51588
  • router: support layout/special files as direct children of parallel routes: #​51604
  • use env var to switch next.js to turbopack mode: #​51353
  • Revert "add edge rendering for app dir for Turbopack": #​51617
  • Ensure upgrade request has request meta: #​51590
  • Revert "Fix standalone not found": #​51506
Documentation Changes
  • docs: Add streaming AI example.: #​51382
  • docs: remove copy mentioning appDir as an experimental feature: #​51403
  • examples: update with-supabase example to App Router: #​51335
  • Fix typo in image alt: #​51487
  • docs: add better examples to next/image docs.: #​51457
  • Go directly to caching section: #​51501
  • fix(typo): add missing word: #​51490
  • fix(typo): add missing comma: #​51489
  • Remove duplicate bullet point in app router migration docs: #​51440
  • fix: missing come: #​51437
  • Linted MDX: #​51530
  • docs: Fix typo: #​51517
  • Migrate validate links script from next-site and setup GitHub action: #​51365
  • Remove extra word in env key error: #​51512
  • Remove duplicate word in 11-draft-mode.mdx: #​51580
  • Broken link at 01-static-and-dynamic-rendering.mdx: #​51582
  • refactor tests for readability: #​51051
Example Changes
  • Upgrade with-redux example to app router: #​49994
Misc Changes
Credits

Huge thanks to @​wyattjoh, @​ijjk, @​dvakatsiienko, @​leerob, @​kwonoj, @​nickmccurdy, @​brunoeduardodev, @​dijonmusters, @​shuding, @​tyler-lutz, @​huozhi, @​feedthejim, @​alexkirsz, @​sonam-serchan, @​vicsantizo, @​leodr, @​wiscaksono, @​sokra, @​delbaoliveira, @​ztanner, @​hustLer2k, @​joshuabaker, and @​ForsakenHarmony for helping!

prisma/prisma

v4.16.1

Compare Source

Today, we are issuing the 4.16.1 patch release.

Fixes in Prisma Client

v4.16.0

Compare Source

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

Highlights

This release promotes the following Preview features to General Availability:

  • Prisma Client extensions
  • Ordering by nulls first and last
  • Count by filtered relation
Prisma Client extensions are Generally Available

Today, we’re very excited to announce that Prisma Client extensions are Generally Available and production-ready! This means you can use the feature without the clientExtensions Preview feature flag.🚀

Prisma Client extensions are a powerful new feature for adding functionality on top of your Prisma Client in a type-safe manner. With this feature, you can create simple, but flexible solutions.

Prisma Client extensions have 4 different types of components that can be included in an extension:

  • Result extensions components: add custom fields and methods to query result objects, for example, virtual/computed fields.
  • Model extensions components: enable you to add new methods to your models alongside existing model methods such as findMany.
  • Query extensions components: let you hook into the lifecycle of a query and perform side effects, modify query arguments, or modify the results in a type-safe way. These are an alternative to middleware that provide complete type safety and can be applied in an ad-hoc manner to different extensions.
  • Client extensions components: allow you to add new top-level methods to Prisma Client. You can use this to extend Prisma Client with functionality that isn’t tied to specific models.
const prisma = new PrismaClient().$extends({
  name: "extension-name",
  result: { /* ... */ },
  model: { /* ... */ },
  query: { /* ... */ },
  client: { /* ... */ },
});

You can also create and publish extensions for others to use. Learn more about how to share extensions in our documentation.

More features and changes made to Client Extensions

We also made the following improvements to Prisma Client extensions in preparation for General Availability:

  • Added a top-level $allOperations method for query component that captures all model operations as well as top-level raw queries. Refer to our documentation for more information.

    const prisma = new PrismaClient().$extends({
  query: {
    $allOperations({ args, query, operation, model }) {
      /* your extension's logic here */
    }
  }
})

  • Prisma.validator can now also be used for extended types:

    const prisma = new PrismaClient().$extends({/* ... */})
const data = Prisma.validator(prisma, 'user', 'findFirst', 'select')({
  id: true,
})

  • query callbacks for $queryRaw and $executeRaw will always receive Sql instance as args. This instance can be used to compose a new query using Prisma.sql:

    const prisma = new PrismaClient().$extends({
  query: {
    $queryRaw({ args, query }) {
      return query(Prisma.sql`START TRANSACTION; ${args}; COMMIT;`)
    }
  }
})

  • $on cannot be called after extending Prisma Client. Therefore, if you want to use event handlers together with extensions, we recommend using the $on method before $extends.

    const prisma = new PrismaClient()
  .$on(/* ... */)
  .$extends({/* ... */})

  • We updated the import path for utilities used for authoring extension to @prisma/client/extension rather than @prisma/client

    + import { Prisma } from "@​prisma/client/extension"
- import { Prisma } from "@​prisma/client"
Deprecating Middleware

We also took this opportunity to deprecate Prisma Client’s middleware. We recommend using to using Prisma Client query extension components which can be used to achieve the same functionality and with better type safety.

🚧 Middleware will still be available in Prisma Client’s API. However, we recommend using Prisma Client extensions over middleware.

Ordering by nulls first and last is now Generally Available

Starting with this release, we’re excited to announce that orderByNulls is now Generally Available! This means you can use the feature without the orderByNulls Preview feature flag.🌟

We introduced this feature in 4.1.0 to enable you to sort records with null fields to either appear at the beginning or end of the result.

The following example query sorts posts by updatedAt, with records having a null value at the end of the list:

await prisma.post.findMany({
  orderBy: {
    updatedAt: { sort: 'asc', nulls: 'last' },
  },
})

To learn more about this feature, refer to our documentation.

We’re excited to see what you will build! Feel free to share with us what you build on Twitter, Slack, or Discord.

Count by filtered relation is now Generally Available

This release moves the filteredRelationCount Preview feature to General Availability! This means you can use the feature without the filteredRelationCount Preview feature flag.

We first introduced this feature in 4.3.0 to add the ability to count by filtered relations.

The following query, for example, counts all posts with the title “Hello!”:

await prisma.user.findMany({
  select: {
    _count: {
      select: {
        posts: { where: { title: 'Hello!' } },
      },
    },
  },
})

To learn more about this feature, refer to our documentation.

Introspection warnings for expression indexes

In the last two releases, 4.13.0 and 4.14.0, we added 9 introspection warnings. These warnings surface features in use in your database that cannot currently be represented in the Prisma schema.

In this release, we’re adding one more introspection warning to the list: expression indexes.

On database introspection, the Prisma CLI will surface the feature with a warning, and a comment in your Prisma schema for sections for each feature in use. The warnings will also contain instructions for workarounds on how to use the feature.

Fixes and improvements

Prisma Client
Prisma Migrate
Language tools (e.g. VS Code)
Prisma Studio

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 22 at 5 pm Berlin | 8 am San Francisco.

framer/motion

v10.12.17

Compare Source

Fixed
  • Fixing useInstantTransition when called on subsequent frames.
  • Fixing reverse animation with negative speed finishes too early when the
    time is set to the duration.
garmeeh/next-seo

v6.1.0

Compare Source

vercel/swr

v2.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: vercel/swr@v2.1.5...v2.2.0

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (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.

@ijsblokjeee ijsblokjeee bot added Dependencies 🚀 PRs and Issues related to dependencies Chore 🧹 labels Jun 25, 2023
@kodiakhq kodiakhq bot merged commit 0765ab6 into main Jun 25, 2023
5 checks passed
@kodiakhq kodiakhq bot deleted the renovate/all-non-major branch June 25, 2023 00:14
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
Chore 🧹 Dependencies 🚀 PRs and Issues related to dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants