chore(deps): update all non-major dependencies #180
Merged
+21
−15
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
❌ Deploy Preview for bun-query-builder failed. Why did it fail? →
|
commit: |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
03c8cdd to
761f7b5
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
761f7b5 to
c3402ee
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
c3402ee to
6a259e6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
b1091dd to
05508a9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
05508a9 to
0a1ba84
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:
^6.19.0-integration-next.14->^6.19.0^0.4.7->^0.4.8^1.3.1->^1.3.2^6.19.0-integration-next.14->^6.19.0Release Notes
prisma/prisma (@prisma/client)
v6.19.0Compare Source
v6.19.0-integration-next.22Compare Source
v6.19.0-integration-next.21Compare Source
stacksjs/ts-validation (@stacksjs/ts-validation)
v0.4.8Compare Source
No significant changes
View changes on GitHub
prisma/prisma (prisma)
v6.19.0Compare Source
Today, we are excited to share the
6.19.0stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X
Highlights
This release brings a lot of bug fixes and improvements to both the ORM and Prisma Postgres.
Prisma ORM
Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:
Prisma Postgres
Prisma Postgres is our fully managed Postgres service, designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release, we are introducing the following improvements:
Connection pooling with Prisma Postgres
We added support for direct connections in 6.17, opening Prisma Postgres up to working with any tool in the wider Postgres ecosystem. Now, you can confirm that connection to support connection pooling by appending the query parameter
pool=trueto the connection string.To make this even more accessible, from the Prisma Postgres console, when getting your database credentials, we’ve updated the UI to easily toggle between pooled and un-pooled.
VS Code extension
A frequently requested feature is to be able to use a local Prisma Postgres database within our VS Code Extension without having to log in. In this release, we’re happy to share that this is now supported! Now you can work on your project without having to connect to the database remotely.
#1924: previewFeatures = "" suggestion results in "[]" value
Preparing for Prisma v7
Prisma v7 is almost here, and we’ve been making many of the feature in it available ahead of its release. If you haven’t been keeping your version of
prisma,@prisma/clientup to date, now is the time to do so before the release. Many of the changes we’ve introduced over the 6.x release cycle will become the default in v7.prisma-client-jsprisma-clientengineanddatasourcekeys inprisma.config.tsOpen roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
v6.19.0-integration-next.22Compare Source
v6.19.0-integration-next.21Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.