Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Update all non-major dependencies #323

Merged
merged 1 commit into from
Oct 5, 2023
Merged

Update all non-major dependencies #323

merged 1 commit into from
Oct 5, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@mui/material (source) 5.14.11 -> 5.14.12 age adoption passing confidence
@next/eslint-plugin-next 13.5.3 -> 13.5.4 age adoption passing confidence
@prisma/client (source) 5.3.1 -> 5.4.1 age adoption passing confidence
@storybook/addon-actions (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/addon-essentials (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/addon-interactions (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/addon-links (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/nextjs (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/react (source) 7.4.5 -> 7.4.6 age adoption passing confidence
@storybook/testing-library 0.2.1 -> 0.2.2 age adoption passing confidence
@t3-oss/env-nextjs 0.6.1 -> 0.7.0 age adoption passing confidence
@types/node (source) 18.18.1 -> 18.18.3 age adoption passing confidence
@types/react (source) 18.2.23 -> 18.2.25 age adoption passing confidence
@types/react-dom (source) 18.2.8 -> 18.2.10 age adoption passing confidence
@typescript-eslint/eslint-plugin 6.7.3 -> 6.7.4 age adoption passing confidence
@typescript-eslint/parser 6.7.3 -> 6.7.4 age adoption passing confidence
next (source) 13.5.3 -> 13.5.4 age adoption passing confidence
pino (source) 8.15.1 -> 8.15.6 age adoption passing confidence
prisma (source) 5.3.1 -> 5.4.1 age adoption passing confidence
react-hook-form (source) 7.46.2 -> 7.47.0 age adoption passing confidence
storybook (source) 7.4.5 -> 7.4.6 age adoption passing confidence
zod (source) 3.22.3 -> 3.22.4 age adoption passing confidence

Release Notes

mui/material-ui (@​mui/material)

v5.14.12

Compare Source

Oct 3, 2023

A big thanks to the 17 contributors who made this release possible. Here are some highlights ✨:

@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
@mui/[email protected]
Docs
Core

All contributors of this release in alphabetical order: @​alexfauquette, @​brijeshb42, @​DanailH, @​danilo-leal, @​DiegoAndai, @​Erik-McKelvey, @​Janpot, @​mj12albert, @​mnajdova, @​oliviertassinari, @​romgrk, @​sai6855, @​Semigradsky, @​siriwatknp, @​xulingzhihou, @​zanivan, @​ZeeshanTamboli

vercel/next.js (@​next/eslint-plugin-next)

v13.5.4

Compare Source

Core Changes
  • chore: NextJS -> Next.js: #​55961
  • fix-failed-to-generate-self-signed-certificate issue:#​55891: #​55947
  • Remove .test.js from dist: #​55946
  • Turbopack next/font/google: don't insert css rules for multiple weights or styles: #​55852
  • Fix stale revalidate stream handling: #​55978
  • turbopack: improve turbopack/test stability: #​56024
  • Mark testmode fetches internal: #​56036
  • chore: Remove 'beta.' Subdomain from beta.nextjs.org Links: #​55924
  • Remove experimental.sharedPool: #​56021
  • fix(worker): pass env to build worker w/ config.experimental.workerThreads: #​55257
  • Update swc_core to v0.83.26: #​55780
  • Revert "Update swc_core to v0.83.26": #​56077
  • fix reporting of illegal segments when directory only contains irrelevant files: #​56076
  • Make permanentRedirect return 308 in route handlers: #​56065
  • Remove unneeded next-dev js in next-core: #​56039
  • Fix: Use boolean instead of false for experimental logging config: #​56110
  • chore: remove chalk in favor of picocolors: #​55992
  • Revert: "Generate prefetch RSC payload during build for SSR paths (#​54403)": #​56059
  • fetching logging on edge: #​56108
  • Optimize build trace handling: #​56048
  • Update font data: #​56121
  • feat(turbopack): port bloom filter to nexturbo: #​55678
  • Fixes performance problems due to TaskScopes: #​55721
  • perf: remove react dom legacy from app router: #​56082
  • perf: replace zod with superstruct: #​56083
  • perf: externalise ws for bundled server: #​56095
  • misc: refactor node utils: #​56096
  • Add support for skipTrailingSlashRedirect and skipMiddlewareUrlNormalize in Turbopack: #​56147
  • Add experimental.scrollRestoration for Turbopack: #​56150
  • misc: refactor handleExternals: #​56161
  • perf: add option to bundle pages externals: #​56162
  • Allow jest to run with use server directive: #​56148
  • Update experimental compile cache handling: #​56139
  • App render related code clean up: #​56178
  • Add support for i18n config in Turbopack: #​56182
  • Implement list of config options for Turbopack: #​56188
  • Turbopack: add support for an assetPrefix and basePath: #​56058
  • update turbopack: #​56197
  • Update supported options list to reflect #​56188: #​56200
  • Add support for experimental.logging.level in Turbopack: #​56201
  • Add next.config.js options to turbopack warning file: #​56207
  • fix: @​libsql/client build error: #​56192
  • chore: bump postcss: #​56225
  • Add additional handling for experimental-compile: #​56224
  • Drop ipc server headers filters: #​56226
  • only override NODE_EXTRA_CA_CERTS when using experimental https flag: #​56252
  • Pass same mangling option as terser to SWC minifier: #​56281
  • update turbopack: #​56285
  • clear require cache only when needed: #​56198
  • misc: enable source maps for bundled runtime: #​56289
  • misc: shortcut styled-jsx in external resolution: #​56291
  • Support serverRuntimeConfig and publicRuntimeConfig in Turbopack: #​56310
  • Reland static prefetches & fix prefetch bailout behavior: #​56228
  • fix(#​53190): add missing crossOrigin to assetsPrefix resources: #​56311
  • misc: fix instrumentation with bundled server: #​56318
  • fix(next/client): keep hash when navigating from app to pages router: #​56223
  • fix: support both decoded and encoded url requests of conventioned files : #​56187
  • fix: Invalid URL (404) provided on server actions error: #​56323
  • Revert "misc: shortcut styled-jsx in external resolution (#​56291)": #​56334
  • Fix build output logging order: #​56335
Documentation Changes
  • docs: add not-found to file conventions page: #​55944
  • Update 03-linking-and-navigating.mdx: #​55907
  • docs: Correct place for passing extension option to createMDX(): #​55967
  • docs-55629 update router cache column in cache interactions api table: #​55630
  • Update 03-linking-and-navigating.mdx: #​55969
  • Updates "Prerender Error" page for App Router: #​56044
  • Add the default import alias to create-next-app prompt for clarity: #​55896
  • Update revalidatePath.mdx to fix confusing wording of arguments section.: #​56099
  • docs: Renamed function that is used by other name: #​56170
  • (docs) Document Server Actions .bind method: #​56164
  • docs: Use Response.json over NextResponse.json: #​56173
  • correcting link to useSearchParams ref: #​56169
  • docs(sharp-missing-in-production.mdx): update standalone command: #​56191
  • docs(sharp-missing-in-production.mdx): update standalone command: #​56239
  • Update image.mdx: #​56269
  • Update image.mdx: #​56266
Example Changes
  • chore(examples): bump dependency versions: #​55899
  • Update to with-supertokens example app: #​56035
  • Update dependencies in examples : #​55993
  • Chore/update with supabase demo deploy button: #​52483
  • chore(examples): remove deprecated dependency from with-jest: #​56152
  • chore(examples): fix with-jest types: #​56193
  • (Examples) update Grafbase example: #​54705
  • fix: typo in with-stripe-typescript example: #​56274
Misc Changes
Credits

Huge thanks to @​balazsorban44, @​sdkdeepa, @​aayman997, @​mayank1513, @​timneutkens, @​2XG-DEV, @​eliot-akira, @​hi-matthew, @​riobits, @​wbinnssmith, @​ijjk, @​sokra, @​dvoytenko, @​rishabhpoddar, @​manovotny, @​A7med3bdulBaset, @​huozhi, @​jridgewell, @​joulev, @​SukkaW, @​kdy1, @​feedthejim, @​Fredkiss3, @​styfle, @​MildTomato, @​ForsakenHarmony, @​walfly, @​bzhn, @​shuding, @​boylett, @​Loki899899, @​devrsi0n, @​ImBIOS, @​vinaykulk621, @​ztanner, @​sdaigo, @​hamirmahal, @​blurrah, @​omarmciver, and @​alexBaizeau for helping!

prisma/prisma (@​prisma/client)

v5.4.1

Compare Source

Today, we are issuing the 5.4.1 patch release.

Fix in Prisma Client

v5.4.0

Compare Source

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

Highlights
Preview support for PlanetScale and Neon serverless database drivers

We’re excited to announce Preview support for the Neon and PlanetScale database drivers. The PlanetScale and Neon database drivers allow Prisma to connect to your database using protocols besides TCP — HTTP (PlanetScale) or WebSockets (Neon).

To get started with the serverless database drivers, first enable the driverAdapters Preview feature flag in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters"]
}

Next, to set up Prisma Client to use the serverless database drivers:

PlanetScale

Install the Prisma adapter for PlanetScale and PlanetScale serverless database driver:

npm install @​prisma/adapter-planetscale @​planetscale/database

Update your Prisma Client instance to use the PlanetScale database driver:

// Import required dependencies
import { connect } from '@​planetscale/database';
import { PrismaPlanetScale } from '@​prisma/adapter-planetscale';
import { PrismaClient } from '@​prisma/client';

// Initialize Prisma Client with the PlanetScale serverless database driver
const connection = connect({ url: process.env.DATABASE_URL });
const adapter = new PrismaPlanetScale(connection);
const prisma = new PrismaClient({ adapter });
Neon

Install the Prisma adapter for Neon, Neon database driver and undici (WebSockets):

npm install @​prisma/adapter-neon @​neondatabase/serverless undici

Update your Prisma Client instance to use the Neon serverless database driver:

// Import required dependencies
import { Pool, neonConfig } from '@​neondatabase/serverless';
import { PrismaNeon } from '@​prisma/adapter-neon';
import { PrismaClient } from '@​prisma/client';
import { WebSocket } from 'undici'

neonConfig.webSocketConstructor = WebSocket;

// Initialize Prisma Client with the Neon serverless database driver
const pool = new Pool({ connectionString: process.env.DATABASE_URL });
const adapter = new PrismaNeon(pool);
const prisma = new PrismaClient({ adapter });

Let us know your feedback about the Neon or Planetscale serverless database drivers in the linked GitHub discussions. Create a bug report if you run into any issues.

Early Access support Turso

Turso is an edge-hosted, distributed database that's based on libSQL, an open-source and open-contribution fork of SQLite, enabling you to bring data closer to your application and minimize query latency.

Since support for Turso is in Early Access, there may be some rough edges which we’re still working on it to improve the API and overall support. Additionally, it is behind the driverAdapters Preview feature flag. Enable it to get started using Turso in your project:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["driverAdapters"]
}

Next, install the Prisma Client adapter for Turso and the libSQL database client

npm install @​prisma/adapter-libsql @​libsql/client

Update your Prisma Client instance:

// Import required dependencies
import { PrismaClient } from '@​prisma/client'
import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { createClient } from '@​libsql/client'

// Create a new instance of the libSQL database client
const libsql = createClient({
  // @​ts-expect-error
  url: process.env.TURSO_DATABASE_URL,
  authToken: process.env.TURSO_AUTH_TOKEN 
})

// Create a Prisma "adapter" for libSQL
const adapter = new PrismaLibSQL(libsql)
// Pass the adapter option to the Prisma Client instance
const prisma = new PrismaClient({ adapter })

You can learn more on how to use Prisma together with Turso in the announcement blog post.

Try it out! Let us know what you think and create a bug report if you run into any issues.

Query performance improvements

In our continued efforts to make Prisma Client faster, we identified and improved the performance of different types of queries.

Relation filters improvements

We made the following improvements to relation filters:

  • Removed an unnecessary INNER JOIN used in relation filter queries (Big thank you to @​KhooHaoYit for helping out)
  • Use of LEFT JOIN's for one-to-one relations. Previously, Prisma made use of sub-queries to fetch data.

Example Prisma Client query

prisma.comment.findMany({
  where: {
    post: {
      author: {
        name: "John"
      }
    }
  }
})

Before 5.4.0

SELECT
  "Comment"."id"
FROM
  "Comment"
WHERE
  ("Comment"."id") IN (
    SELECT
      "t0"."id"
    FROM
      "Comment" AS "t0"
      INNER JOIN "Post" AS "j0" ON ("j0"."id") = ("t0"."postId")
    WHERE
      (
        ("j0"."id") IN (
          SELECT
            "t1"."id"
          FROM
            "Post" AS "t1"
            INNER JOIN "User" AS "j1" ON ("j1"."id") = ("t1"."userId")
          WHERE
            (
              "j1"."name" = $ 1
              AND "t1"."id" IS NOT NULL
            )
        )
        AND "t0"."id" IS NOT NULL
      )
  );

After 5.4.0

SELECT
  "Comment"."id"
FROM
  "Comment"
  LEFT JOIN "Post" AS "j1" ON ("j1"."id") = ("Comment"."postId")
  LEFT JOIN "User" AS "j2" ON ("j2"."id") = ("j1"."userId")
WHERE
  (
    "j2"."name" = $ 1
    AND ("j2"."id" IS NOT NULL)
    AND ("j1"."id" IS NOT NULL)
  );

If you’re interested in more details on the relation query filter improvements, you can take a look at this pull request.

Enum improvements on PostgreSQL and CockroachDB

Previously, when an enum value was used in a query, our Postgres driver would make additional queries to resolve the enum types that were used.

In this release, we’re making improvements by casting enums to TEXT to avoid the additional roundtrips when resolving the types.

This change should have the most impact if you’re using pgBouncer or if you’re running Prisma in a serverless environment, where our Postgres driver can’t cache enum types information.

Prisma schema

model User {
  id   Int  @​id @​default(cuid())
  role Role
}

enum Role {
  User
  Admin
}

Prisma Client query

await prisma.user.findMany({ 
  where: {
    role: "Admin"
  }
})

Before 5.4.0

-- Internal driver query
SELECT t.typname, t.typtype, t.typelem, r.rngsubtype, t.typbasetype, n.nspname, t.typrelid FROM pg_catalog.pg_type t LEFT OUTER JOIN pg_catalog.pg_range r ON r.rngtypid = t.oid INNER JOIN pg_catalog.pg_namespace n ON t.typnamespace = n.oid WHERE t.oid = $1;

-- Internal driver query
SELECT enumlabel FROM pg_catalog.pg_enum WHERE enumtypid = $1 ORDER BY enumsortorder;

-- Prisma Client query
SELECT id, role FROM "User" WHERE role = $1;

After 5.4.0

-- Prisma Client query
SELECT id, role::text FROM "User" WHERE role = CAST($1::text AS "Role);
Bulk delete improvements

We optimized the deleteMany operation by:

  • Removing all SELECT queries used to fetch data that would be used as input for the DELETE operation. In some cases, this also improves index usage.
  • Removing the transaction previously used as it’s now a single atomic operation.

Prisma Client query

await prisma.post.deleteMany({
  where: {
    id: {
      gt: 1,
      lt: 10,
    }
  }
})

Before 5.4.0

BEGIN
SELECT id FROM "Post" WHERE id > 1 AND id < 10;
SELECT id FROM "Post" WHERE id > 1 AND id < 10 AND id IN (<...select ids>);
DELETE FROM "Post" WHERE id IN (<...select ids>) AND id > 1 AND id < 10;
COMMIT

After 5.4.0

DELETE FROM "Post" WHERE id > 1 AND id < 10;
Upsert improvements

We improved the upsert operation (non-native database upsert) by removing a redundant SELECT query:

Prisma Client query

await prisma.user.upsert({
  where: { email: "[email protected]" },
  create: { email: "[email protected]", firstName: "John" },
  update: { firstName: "Johnny" },
})

Before 5.4.0

SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?;
SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?;
UPDATE `prisma`.`User` SET `firstName` = ? WHERE `prisma`.`User`.`id` IN (?) AND `prisma`.`User`.`email` = ?;
SELECT `User`.`id` FROM `User` WHERE `User`.`id` = ?;

After 5.4.0

SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?;
UPDATE `prisma`.`User` SET `firstName` = ? WHERE `prisma`.`User`.`id` IN (?) AND `prisma`.`User`.`email` = ?;
SELECT `User`.`id` FROM `User` WHERE `User`.`id` = ?;
Fixes and improvements
Prisma Client
Language tools (e.g. VS Code)
Prisma Engines
Credits

Huge thanks to @​onichandame, @​fqazi, @​KhooHaoYit, @​alencardc, @​Oreilles, @​christianledgard, @​skyzh, @​alula, @​michaelpoellath, @​RobertCraigie, @​icanipa, @​jiashengguo, @​stephenwade, @​darthmaim, @​ludralph, @​Gerschtli, @​andyjy for helping!

💼 We're hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're currently hiring for the following roles:

Feel free to read the job descriptions and apply using the links provided.

storybookjs/storybook (@​storybook/addon-actions)

Configuration

📅 Schedule: Branch creation - "every weekend" (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.

@renovate renovate bot added the renovate label Oct 1, 2023
@vercel
Copy link

vercel bot commented Oct 1, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
my-nextjs-starter ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 5, 2023 3:54pm

@renovate renovate bot changed the title Update dependency pino to v8.15.2 Update all non-major dependencies Oct 1, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5ef291f to 18d6f2f Compare October 1, 2023 12:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 18d6f2f to 8a5fb01 Compare October 2, 2023 06:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8a5fb01 to 11e8293 Compare October 2, 2023 10:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 11e8293 to 0e31adc Compare October 2, 2023 19:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0e31adc to b631ce1 Compare October 2, 2023 23:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b631ce1 to 14945fb Compare October 3, 2023 04:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 14945fb to 58ee5a9 Compare October 3, 2023 14:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 58ee5a9 to 3e0bae3 Compare October 3, 2023 20:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3e0bae3 to 5bfd929 Compare October 3, 2023 22:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5bfd929 to 3e4b8ab Compare October 4, 2023 15:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3e4b8ab to 9c77603 Compare October 4, 2023 18:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9c77603 to 374dffe Compare October 4, 2023 23:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 374dffe to d2ef6bc Compare October 5, 2023 10:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d2ef6bc to 4161203 Compare October 5, 2023 15:52
@isoppp isoppp merged commit 28d5f43 into main Oct 5, 2023
2 checks passed
@isoppp isoppp deleted the renovate/all-minor-patch branch October 5, 2023 15:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant