-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update prisma monorepo to v4.16.2 - autoclosed #442
Closed
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
added
Dependencies: Minor
Minor dependencies the Project depends on
Type: Dependencies
All PRs related to dependencies
labels
May 9, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
6 times, most recently
from
May 17, 2023 17:08
e0a07ac
to
b08d756
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.14.0
fix(deps): update prisma monorepo to v4.14.1
May 17, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
4 times, most recently
from
May 23, 2023 18:23
16f9639
to
e11f8cb
Compare
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
2 times, most recently
from
May 25, 2023 03:12
7838748
to
bf0b82e
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.14.1
fix(deps): update prisma monorepo to v4.14.1 - autoclosed
May 25, 2023
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.14.1 - autoclosed
fix(deps): update prisma monorepo to v4.14.1
May 30, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
from
May 30, 2023 17:53
bf0b82e
to
e023c8b
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.14.1
fix(deps): update prisma monorepo to v4.15.0
May 30, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
5 times, most recently
from
June 6, 2023 15:45
97aa205
to
fd0775d
Compare
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
6 times, most recently
from
June 14, 2023 16:32
f5dbaed
to
08aa59f
Compare
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
4 times, most recently
from
June 20, 2023 13:37
987ba4d
to
5f261e6
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.15.0
fix(deps): update prisma monorepo to v4.16.0
Jun 20, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
3 times, most recently
from
June 22, 2023 16:46
f9bdf2e
to
48856f6
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.16.0
fix(deps): update prisma monorepo to v4.16.1
Jun 22, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
5 times, most recently
from
June 30, 2023 15:22
046b67c
to
1c4ce89
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.16.1
fix(deps): update prisma monorepo to v4.16.2
Jun 30, 2023
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
5 times, most recently
from
July 6, 2023 17:53
cbbf4a9
to
80f3cdd
Compare
renovate
bot
force-pushed
the
renovate/prisma-monorepo
branch
from
July 7, 2023 17:17
80f3cdd
to
45d0377
Compare
renovate
bot
changed the title
fix(deps): update prisma monorepo to v4.16.2
fix(deps): update prisma monorepo to v4.16.2 - autoclosed
Jul 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Dependencies: Minor
Minor dependencies the Project depends on
Type: Dependencies
All PRs related to dependencies
0 participants
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:
4.14.1
->4.16.2
4.14.1
->4.16.2
Release Notes
prisma/prisma (@prisma/client)
v4.16.2
Compare Source
Today, we are issuing the
4.16.2
patch release.Fixes in Prisma Client
$allModels: { $allOperations }
sets query type tonever
undefined
explicitly passed toselect
/include
v4.16.1
Compare Source
Today, we are issuing the
4.16.1
patch release.Fixes in Prisma Client
$extend
in factory function whencompilerOptions.composite
istrue
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 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:
findMany
.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 forquery
component that captures all model operations as well as top-level raw queries. Refer to our documentation for more information.Prisma.validator
can now also be used for extended types:query
callbacks for$queryRaw
and$executeRaw
will always receiveSql
instance asargs
. This instance can be used to compose a new query usingPrisma.sql
:$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
.We updated the import path for utilities used for authoring extension to
@prisma/client/extension
rather than@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.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 theorderByNulls
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: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 thefilteredRelationCount
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!”:
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
select
'd explicitly.prisma generate
when running it directly after installingprisma
$runCommandRaw
is not passing the expected data to middleware or client extension.prismaVersion.client
available on "@prisma/client/scripts/default-index"distinct
fieldPrisma.validator
clientExtensions
GA$queryRawUnsafe
also triggers$allModels.$allOperations
$on
applied to an extended client is also bound to the parent client$queryRaw*
is broken in interactive transactions together withclientExtensions
in4.16.0-dev.17
Prisma Migrate
type
sprisma db pull
gets rid of@default(uuid())
on re-introspectionLanguage tools (e.g. VS Code)
Go to Definition
does not work when target model contains a field with a type name that starts with the same namePrisma Studio
Error: spawn xdg-open ENOENT
onprisma 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.
v4.15.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
For this release, we focused on fixing bugs and making smaller quality-of-life improvements.
Support for custom arguments for
prisma db seed
This release adds support for defining and passing arbitrary arguments to
prisma db seed
. This creates the opportunity for you to define your own arguments in your seed file that you could pass to theprisma db seed
command. A few example use-cases include, but are not limited to:Here is an example
seed.ts
file that defines custom arguments for seeding different data in different environments:You can then provide the
environment
argument when executing the seed script as follows:Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.
Improved error messages when Query Engine file is not found
This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:
We hope these error messages are helpful while debugging your application.
Prisma VS Code extension improvements
In this release, we made a few improvements to our VS Code extension:
Updated the file system watcher that is responsible for restarting the TypeScript server when
prisma generate
is run to ensure the types are in syncAdded Quick Fixes action for unique identifiers for MongoDB to add the
@map("_id")
attribute function when it’s missing on an identifier fieldScreen.Recording.2023-05-17.at.19.22.20.mov
Support for renaming symbols for composite types and views
type-symbol-rename.mov
Fixes and improvements
Prisma Client
Error: write EPIPE
on WSL <-> Windowsprisma generate
is blocked byquery-engine-rhel-openssl-1.0.x
opening in Notepad on Windowsnode_modules
(from another platform) leads to platform engine not being presentoutput
Query engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.x
Cannot find name '$PrismaModel'
due to featureextendedWhereUnique
with preview featurefieldReference
Date
values silently turn intonulls
fieldReference
is not working with enumsPrisma Migrate
prisma db seed
to the seed commandLanguage tools (e.g. VS Code)
@map("_id")
annotationCredits
Huge thanks to @RobertCraigie, @KhooHaoYit, @art049, @luxaritas, @mrazauskas, @maxmartynov, @haneenmahd for helping!
📺 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 1 at 5 pm Berlin | 8 am San Francisco.
Configuration
📅 Schedule: Branch creation - "before 6pm every weekday" in timezone Asia/Kolkata, Automerge - "after 9pm every weekday" in timezone Asia/Kolkata.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.