This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
chore(deps): update all non-major dependencies #423
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
ijsblokjeee
bot
added
Dependencies 🚀
renovate
bot
force-pushed
the
renovate/all-non-major
branch
14 times, most recently
from
64a9aa3 to
20b8b40
Compare
renovate
bot
force-pushed
the
renovate/all-non-major
branch
6 times, most recently
from
d65bc67 to
8bbbc0d
Compare
renovate
bot
force-pushed
the
renovate/all-non-major
branch
from
8bbbc0d to
b87ead2
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.3.1->^3.3.213.5.2->13.5.4^5.3.1->^5.4.2^1.0.4->^1.0.5^1.0.3->^1.0.4^1.0.4->^1.0.5^2.0.5->^2.0.6^1.0.4->^1.0.5^1.1.4->^1.1.5^1.0.6->^1.0.7^4.35.3->^4.36.18.10.1->8.10.6^10.38.3->^10.40.0^10.38.3->^10.40.0^10.38.3->^10.40.0^10.38.2->^10.40.0^1.5.0->^1.5.1^3.0.0->^3.1.0^7.0.2->^7.1.1^0.279.0->^0.286.0^13.5.2->^13.5.4^5.3.1->^5.4.2^7.46.2->^7.47.0^1.13.1->^1.13.3^2.2.2->^2.2.4^3.10.0->^3.11.0^3.22.2->^3.22.4Release Notes
react-hook-form/resolvers (@hookform/resolvers)
v3.3.2Compare Source
Bug Fixes
zoddependency (#633) (1baed6e)vercel/next.js (@next/font)
v13.5.4Compare Source
Core Changes
beta.nextjs.orgLinks: #55924config.experimental.workerThreads: #55257swc_coretov0.83.26: #55780swc_coretov0.83.26": #56077permanentRedirectreturn 308 in route handlers: #56065booleaninstead offalsefor experimental logging config: #56110postcss: #56225Documentation Changes
not-foundto file conventions page: #55944extensionoption tocreateMDX(): #55967.bindmethod: #56164Response.jsonoverNextResponse.json: #56173Example Changes
with-jest: #56152with-jesttypes: #56193with-stripe-typescriptexample: #56274Misc Changes
swc_coretov0.83.28: #56134Credits
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!
v13.5.3Compare Source
Core Changes
build: #55628fs.existsSyncinstead ofaccessSync: #55675next/dist/esmrewriteResolvePlugin: #55689fetchServerResponseis a valid record when stored in router cache: #55690next/navigation: #55743generate_typestask: #55748next infooutput: #55704--experimental-https: #55775turbopack-230922.2: #55828--experimental-https: #55775turbopack-230922.2: #55828Documentation Changes
useFormState: #55564Example Changes
Misc Changes
nissuer: #55723dependencies/devDependencies: #55730Credits
Huge thanks to @sokra, @ztanner, @anonrig, @huozhi, @mayank1513, @travisanderson, @wyattjoh, @jridgewell, @ryanagillie, @Brooooooklyn, @kwonoj, @balazsorban44, @naruaway, @S3Prototype, @feedthejim, @joulev, @icyJoseph, @ijjk, @ForsakenHarmony, @timneutkens, @wbinnssmith, @sdkdeepa, @sdaigo, @leerob, @dominiksipowicz, @joao-vasconcelos, and @mostafaegouda for helping!
prisma/prisma (@prisma/client)
v5.4.2Compare Source
Today, we are issuing the
5.4.2patch release.Fix in Prisma Client
v5.4.1Compare Source
Today, we are issuing the
5.4.1patch release.Fix in Prisma Client
….findMany()invocation: The columnj1.iddoes not exist in the current database.Fix in
@prisma/adapter-planetscalev5.4.0Compare 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 serverless database drivers. The PlanetScale and Neon serverless 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
driverAdaptersPreview feature flag in your Prisma schema:Next, to set up Prisma Client to use the serverless database drivers:
PlanetScale
Install the Prisma adapter for PlanetScale and PlanetScale serverless database driver, and undici:
Ensure you update the host value in your connection string to
aws.connect.psdb.cloud. You can learn more about this here.DATABASE_URL='mysql://johndoe:strongpassword@aws.connect.psdb.cloud/clear_nightsky?sslaccept=strict'Update your Prisma Client instance to use the PlanetScale database driver:
Neon
Install the Prisma adapter for Neon, Neon serverless database driver and undici (WebSockets):
Update your Prisma Client instance to use the Neon serverless database driver:
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 for 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
driverAdaptersPreview feature flag. Enable it to get started using Turso in your project:Next, install the Prisma Client adapter for Turso and the
libSQLdatabase clientUpdate your Prisma Client instance:
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:
INNER JOINused in relation filter queries (Big thank you to @KhooHaoYit for helping out)LEFT JOIN's for to-one relations. Previously, Prisma made use of sub-queries to fetch data.Example Prisma Client query
Before 5.4.0
After 5.4.0
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
TEXTto avoid the additional roundtrips when resolving the types.This change should have the most impact if you’re using
pgBounceror if you’re running Prisma in a serverless environment, where our Postgres driver can’t cache enum types information.Prisma schema
Prisma Client query
Before 5.4.0
After 5.4.0
Bulk delete improvements
We optimized the
deleteManyoperation by:SELECTqueries used to fetch data that would be used as input for theDELETEoperation. In some cases, this also improves index usage.Prisma Client query
Before 5.4.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.
This PR has been generated by Mend Renovate. View repository job log here.