chore(deps): update all non-major dependencies #139
Merged
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.13.5
->2.13.7
2.7.3
->2.7.4
2.7.3
->2.7.4
4.4.0
->4.5.0
29.1.2
->29.2.0
5.40.0
->5.40.1
5.40.0
->5.40.1
2.5.23
->2.5.26
27.1.1
->27.1.3
29.1.2
->29.2.1
4.4.0
->4.5.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v2.13.7
Compare Source
Patch Changes
8473682c4
Thanks @charlypoly! - ensure to generatecodegen.ts
in a typescript setupv2.13.6
Compare Source
Patch Changes
c4d9566c7
Thanks @vhenzl! - FixexecuteHooks
to quote args for shell commanddotansimha/graphql-code-generator (@graphql-codegen/typescript)
v2.7.4
Compare Source
Patch Changes
1bd7f771c
]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v2.7.4
Compare Source
Patch Changes
1bd7f771c
]:prisma/prisma
v4.5.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟
Major improvements
Filter for non-unique properties in unique where queries (Preview)
In this release, we are adding support for non-unique properties inside the
where
statement for queries that operate on a unique record (e.g.:findUnique
,update
,delete
, etc.). This was not possible in the past, as we only allowed unique fields as filters inside thewhere
statement for the queries in question.There are use cases where a query that operates on a unique record requires further filtering by non-unique properties. For example, for the following model:
Let’s say that you would like to update the
Article
with anid
of “5”, but only if theversion
equals "1":With
4.5.0
, we are adding support to specify any number of non-unique fields in yourwhere
statement, as long as you have at least one unique field.To use it, enable the Preview feature flag:
To learn more about this feature and about use cases where it can be useful, please check out our documentation. For feedback, please leave a comment on the GitHub issue.
PostgreSQL extension management (Preview)
We are excited to add support for declaring PostgreSQL extensions in the Prisma schema. The feature comes with support for introspection and migrations. This will allow you to adopt, evolve and manage which PostgreSQL database extensions are installed directly from within your Prisma schema.
To try this feature, enable the Preview feature flag:
Now you will be able to use the new
extensions
property in thedatasource
block of your Prisma schema.Please visit our documentation to learn more about this feature or leave a comment with feedback on the GitHub issue.
Change to Referential Integrity — property in
datasource
block renamed torelationMode
(Preview)To prepare Prisma Client’s emulation of relations for general availability, we are releasing several improvements to the
referentialIntegrity
Preview feature.We decided to rename the feature to Relation Mode. We think this closer reflects what this feature does and distinguishes it from integrity management on the database level. The related property in the
datasource
block of the Prisma schema has also been changed fromreferentialIntegrity
torelationMode
.To use it, keep using the old
referentialIntegrity
Preview feature flag:But use the new property name in the
datasource
:We also removed the referential action
NoAction
for PostgreSQL and SQLite when usingrelationMode = "prisma"
as we are not planning to support the details of the database behavior.To learn more about
relationMode
, please check out the documentation or leave a comment on the GitHub issue.Deno for Prisma Client for Data Proxy (Preview)
Deno is an alternative JavaScript runtime that can replace Node.js to run JS and TS apps. It aligns itself closely with web technologies, claims to be secure by default, and supports TypeScript out of the box.
Today we are releasing initial support for Prisma with Deno via an integration for our Prisma Client for Data Proxy. This feature was developed together with the amazing team at Deno 🦕.
To use Prisma Client in a Deno project, add the
deno
Preview feature flag to your Prisma schema and define a folder asoutput
(this is required for Deno):Now you can generate Prisma Client with the Data Proxy using the command
npx prisma generate --data-proxy
. Then use Prisma Client in your Deno script with the following import:You can also deploy an app built and configured like this on Deno Deploy, Deno’s deployment platform. Read this guide in our documentation for a full example and individual steps.
For feedback, please comment on this GitHub issue.
Fixed “Invalid string length” error in Prisma Studio and Prisma Data Platform Data Browser
Many people were having issues with an "Invalid string length" error both in Prisma Studio and Prisma Data Platform Data Browser. This issue can be resolved through this workaround. With this release, the root cause of this issue has been fixed and it should not occur again.
Updated proposal for Client Extensions: request for comments
In
4.3.0
, we shared a proposal for Prisma Client Extensions on Github. We received a lot of great feedback, which we have incorporated into a new proposal.If you’re interested, please head over to the new proposal in GitHub and tell us what you think. Thank you!
Fixes and improvements
Prisma
onDelete: setDefault
referentialIntegrity
modes makes migration history obsoletereferentialIntegrity
andrelationMode
Prisma Client
Prisma Migrate
postgresqlExtensions
:migrate dev
errors withERROR: type "citext" does not exist
when settingextensions = [citext]
Language tools (e.g. VS Code)
relationMode
(previouslyreferentialIntegrity
) in the datasource blockCredits
Huge thanks to @kt3k, @abenhamdine, @jsoref for helping!
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.40.1
Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.40.1
Compare Source
Note: Version bump only for package @typescript-eslint/parser
vercel/vercel
v2.5.26
Compare Source
v2.5.25
Compare Source
v2.5.24
Compare Source
jest-community/eslint-plugin-jest
v27.1.3
Compare Source
Bug Fixes
jest()
(#1269) (4450daa)v27.1.2
Compare Source
Bug Fixes
facebook/jest
v29.2.1
Compare Source
Features
[@jest/globals, jest-mock]
Addjest.Spied*
utility types (#13440)Fixes
[jest-environment-node]
makeglobalThis.performance
writable for Node 19 and fake timers (#13467)[jest-mock]
Revert #13398 to restore mocking of setters (#13472)Performance
[*]
Use sha1 instead of sha256 for hashing (#13421)v29.2.0
Compare Source
Features
[@jest/cli, jest-config]
A seed for the test run will be randomly generated, or set by a CLI option (#13400)[@jest/cli, jest-config]
--show-seed
will display the seed value in the report, and can be set via a CLI flag or through the config file (#13400)[jest-config]
AddreadInitialConfig
utility function (#13356)[jest-core]
AllowtestResultsProcessor
to be async (#13343)[@jest/environment, jest-environment-node, jest-environment-jsdom, jest-runtime]
AddgetSeed()
to thejest
object (#13400)[expect, @​jest/expect-utils]
AllowisA
utility to take a type argument (#13355)[expect]
ExposeAsyncExpectationResult
andSyncExpectationResult
types (#13411)Fixes
[babel-plugin-jest-hoist]
IgnoreTSTypeQuery
when checking for hoisted references (#13367)[jest-core]
FixdetectOpenHandles
false positives for some special objects such asTLSWRAP
(#13414)[jest-mock]
Fix mocking of getters and setters on classes (#13398)[jest-reporters]
Revert: Transform file paths into hyperlinks (#13399)[@jest/types]
Infer type ofeach
table correctly when the table is a tuple or array (#13381)[@jest/types]
Rework typings to allow the*ReturnedWith
matchers to be called with no argument (#13385)Chore & Maintenance
[*]
Update@babel/*
deps, resulting in slightly different stack traces foreach
(#13422)Performance
[jest-runner]
Do not instrument v8 coverage data if coverage should not be collected (#13282)Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (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.