-
Notifications
You must be signed in to change notification settings - Fork 156
chore(deps): update all non-major dependencies #3515
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.
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,286
−1,784
Conversation
This file contains hidden or 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
commit: |
124c605
to
0782406
Compare
0782406
to
22de68a
Compare
22de68a
to
99d754d
Compare
99d754d
to
27ada58
Compare
27ada58
to
ef88a00
Compare
ef88a00
to
5055e54
Compare
5055e54
to
67f00d0
Compare
67f00d0
to
e20f066
Compare
e20f066
to
209c9a3
Compare
209c9a3
to
e802d03
Compare
e802d03
to
c0bca10
Compare
c0bca10
to
ca521ff
Compare
ca521ff
to
9b893b5
Compare
3958d36
to
06d47b2
Compare
06d47b2
to
80d6d59
Compare
80d6d59
to
80f5cae
Compare
80f5cae
to
4fe1f20
Compare
4fe1f20
to
13c8e3e
Compare
13c8e3e
to
0f5384d
Compare
0f5384d
to
789c571
Compare
789c571
to
e729fd2
Compare
e729fd2
to
2f18c8b
Compare
2f18c8b
to
b1a7494
Compare
b1a7494
to
a204698
Compare
a204698
to
5ea6dde
Compare
5ea6dde
to
f382594
Compare
f382594
to
28318a5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
2.9.1
->2.10.0
13.1.0
->13.5.0
6.9.0
->6.12.0
3.6.0
->3.8.0
1.1.6
->1.1.7
9.0.15
->9.0.17
9.0.15
->9.0.17
9.0.15
->9.0.17
9.0.15
->9.0.17
9.0.15
->9.0.17
2.22.2
->2.24.0
2.3.12
->2.4.0
6.0.0
->6.1.0
1.12.4
->1.14.0
1.2.16
->1.2.18
24.0.3
->24.0.14
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
1.18.2
->1.18.3
3.16.5
->3.16.13
1.11.13
->1.12.2
8.0.2
->8.0.3
15.3.3
->15.4.1
5.0.0-beta.27
->5.0.0-beta.29
3.17.5
->3.17.7
3.5.3
->3.6.2
6.9.0
->6.12.0
7.57.0
->7.60.0
3.6.0
->3.8.0
9.0.15
->9.0.17
5.35.2
->5.36.2
0.2.2
->0.2.4
44.2.7
->44.4.1
0.5.7
->0.5.8
7.0.2
->7.0.4
Release Notes
nextauthjs/next-auth (@auth/prisma-adapter)
v2.10.0
Compare Source
Bugfixes
9866f71
)icons-pack/react-simple-icons (@icons-pack/react-simple-icons)
v13.5.0
Compare Source
Minor Changes
f99d420
Thanks@LitoMore! - Bump simple-icons@15.6.0
v13.4.0
Compare Source
Minor Changes
8f2ba95
Thanks@LitoMore! - Bump simple-icons@15.5.0
v13.3.0
Compare Source
Minor Changes
18dc2d8
Thanks@LitoMore! - Bump simple-icons@15.4.0
v13.2.0
Compare Source
Minor Changes
965029b
Thanks@LitoMore! - Bump simple-icons@15.3.0
prisma/prisma (@prisma/client)
v6.12.0
Compare Source
Today, we are excited to share the
6.12.0
stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
ESM-compatible
prisma-client
generator now in PreviewWe’re excited to share that our new and more flexible
prisma-client
generator is moving into Preview! As a reminder, here’s what it looks like:This new generator eliminates any headaches that you may have experienced due to magical code generation into
node_modules
and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:
📚 Learn more in the docs.
Specify
views
andmigrations
folder locations inprisma.config.ts
(Early Access)As we’re getting closer to the General Availability release of
prisma.config.ts
, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations
andviews
) to give you more flexibility and clarity on how to locate these files:📚 Learn more in the docs.
v6.11.1
Compare Source
Today, we are issuing a 6.11.1 patch release.
Bug fixes
In Prisma ORM version 6.11.0, we shipped a bug fix for Prisma that allows using Prisma Postgres with direct TCP connections with Prisma Driver Adapters. This fix, however, required refactoring the of the Prisma Client initialization logic, and while several test cases were added, an edge case was missing, causing https://github.com/prisma/prisma/issues/27569.
Namely, using
@prisma/client
with@prisma/extension-accelerate
on aprisma+postgres://...
connection string, while generating the Prisma Client definitions viaprisma generate
, resulted in aPrismaClientInitializationError
.This is now fixed, so we highly recommend upgrading to version 6.11.1.
Reminder: when using Prisma Accelerate, we highly encourage you to generate your Prisma Client definitions via
prisma generate --no-engine
.We've fixed an issue that would occur when using arrays as aggregation fields with the query compiler. These queries would fail with a confusing data mapping error. They should now work as expected.
v6.11.0
Compare Source
Today, we are excited to share the
6.11.0
stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
Prisma ORM without Rust engines for MySQL/MariaDB, Neon & CockroachDB (Preview)
We are in the process of removing the Rust engines from Prisma ORM. This week, we're adding Preview support for the Rust-free Prisma ORM version for MySQL via a new
@prisma/adapter-mariadb
driver adapter, as well as for Neon and CockroachDB via the already existing@prisma/adapter-neon
and@prisma/adapter-pg
adapters.To use it, enable the
queryCompiler
anddriverAdapters
feature flags on yourgenerator
block, install the driver adapter for your database and start querying!📚Learn more in the docs.
Stop and remove local Prisma Postgres instances via CLI
You can start a local Prisma Postgres instance using the
prisma dev --name mydb
command or via the Prisma VS Code extension UI.If you start a local instance via the Prisma CLI, you can simply kill the process to stop the instance. However, when you start instances via the VS Code extension UI, you could also only stop them via the UI—not via the CLI.
This changes in this release: You can now also stop local Prisma Postgres instances and remove them from your file system via the Prisma CLI:
prisma dev stop <globs>
: Stops one or more local Prisma Postgres instancesprisma dev rm <globs>
: Removes one or more local Prisma Postgres instances from your file system📚Learn more in the docs.
Ready-to-run examples for new
prisma-client
generatorOur new
prisma-client
generator is more flexible, provides more control about the generated code, works with various JS runtimes and comes with ESM support out-of-the-box.To make it easier for you to try it out, we created a few ready-to-run example projects so you can see the new generator in action:
nextjs-starter-webpack
nextjs-starter-turbopack
neextjs-starter-webpack-monorepo
nextjs-starter-webpack-with-middleware
Bug fixes in VS Code embedded Prisma Studio
Have you already seen the new look of Prisma Studio when it's embedded directly in VS Code via the Prisma VS Code extension? In this release, we fixed a few bugs that you all have reported:
Let us know in case you hit any snags with Prisma ORM by opening a new issue.
Other news
Embed Prisma Studio in your own tools and projects
If you're using Prisma Postgres (yourself or by offering it to your own users), you can now embed Prisma Studio to offer an amazing data editing experience to your users via the
@prisma/studio-core
npmConfiguration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 was generated by Mend Renovate. View the repository job log.