fix(deps): update all non-major dependencies
This PR contains the following updates:
Release Notes
apollographql/apollo-client (@apollo/client)
v3.10.4
Patch Changes
-
#11838
8475346Thanks @alex-kinokon! - Don’t prompt for DevTools installation for browser extension page -
#11839
6481fe1Thanks @jerelmiller! - Fix a regression in 3.9.5 where a merge function that returned an incomplete result would not allow the client to refetch in order to fulfill the query. -
#11844
86984f2Thanks @jerelmiller! - Honor the@nonreactivedirective when usingcache.watchFragmentor theuseFragmenthook to avoid rerendering when using these directives. -
#11824
47ad806Thanks @phryneas! - Create brandedQueryReftype without exposed properties.This change deprecates
QueryReferencein favor of aQueryReftype that doesn't expose any properties. This change also updatespreloadQueryto return a newPreloadedQueryReftype, which exposes thetoPromisefunction as it does today. This means that query refs produced byuseBackgroundQueryanduseLoadableQuerynow returnQueryReftypes that do not have access to atoPromisefunction, which was never meant to be used in combination with these hooks.While we tend to avoid any types of breaking changes in patch releases as this, this change was necessary to support an upcoming version of the React Server Component integration, which needed to omit the
toPromisefunction that would otherwise have broken at runtime. Note that this is a TypeScript-only change. At runtime,toPromiseis still present on all queryRefs currently created by this package - but we strongly want to discourage you from accessing it in all cases except for thePreloadedQueryRefuse case.Migration is as simple as replacing all references to
QueryReferencewithQueryRef, so it should be possible to do this with a search & replace in most code bases:-import { QueryReference } from '@​apollo/client' +import { QueryRef } from '@​apollo/client' - function Component({ queryRef }: { queryRef: QueryReference<TData> }) { + function Component({ queryRef }: { queryRef: QueryRef<TData> }) { // ... } -
#11845
4c5c820Thanks @jerelmiller! - Remove@nonreactivedirectives from queries passed toMockLinkto ensure they are properly matched. -
#11837
dff15b1Thanks @jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using thecache-and-networkfetch policy.
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
v3.577.0
Note: Version bump only for package @aws-sdk/client-s3
v3.576.0
Features
- client-s3: Updated a few x-id in the http uri traits (dcde25a)
v3.575.0
Note: Version bump only for package @aws-sdk/client-s3
v3.574.0
Note: Version bump only for package @aws-sdk/client-s3
aws/aws-sdk-js-v3 (@aws-sdk/client-ses)
v3.577.0
Note: Version bump only for package @aws-sdk/client-ses
v3.576.0
Note: Version bump only for package @aws-sdk/client-ses
v3.575.0
Note: Version bump only for package @aws-sdk/client-ses
v3.574.0
Note: Version bump only for package @aws-sdk/client-ses
aws/aws-sdk-js-v3 (@aws-sdk/credential-provider-node)
v3.577.0
Note: Version bump only for package @aws-sdk/credential-provider-node
v3.576.0
Note: Version bump only for package @aws-sdk/credential-provider-node
v3.575.0
Note: Version bump only for package @aws-sdk/credential-provider-node
open-telemetry/opentelemetry-js-contrib (@opentelemetry/instrumentation-express)
v0.39.0
prisma/prisma (@prisma/client)
v5.14.0
Today, we are excited to share the 5.14.0 stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release. 🌟
Highlights
Share your feedback about Prisma ORM
We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏
createManyAndReturn()
We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.
Here’s an example of creating multiple posts and then immediately returning those posts.
const postBodies = req.json()['posts']
const posts = prisma.post.createManyAndReturn({
data: postBodies
});
return posts
Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.
const postBodies = req.json()['posts']
const postTitles = prisma.post.createManyAndReturn({
data: postBodies,
select: {
title: true,
},
});
return postTitles
Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.
MongoDB performance improvements
Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.
With 5.14.0, Prisma ORM now rewrites queries to use a combination of $or and $eq operators, leading to dramatic performance increases for queries that include in operators or relation loading.
Fixes and improvements
Prisma Client
-
createMany()should return the created records - Generating Prisma client without any model in its schema
-
MongoDB: Performance issue with nested
takeon many-to-one relationship -
Slow queries on MongoDB using
includefor relations -
[MongoDB] Performance issue in
findMany()query execution within -
MongoDB nested/
includequery slow - MongoDB Connector generates queries which do not take advantage of indices.
- Mongodb Nested Queries Not Using Indexes
-
MongoDB slow delete with
onDelete: SetNull - Slow query with many-to-one relationship on MongoDB
-
prisma init --with-model -
Fixed version of
@opentelemetry/*dependencies - Usage of deprecated punycode module
-
Bug: D1 One-to-Many Relation INSERTs fail with
The required connected records were not found.when using indices
Prisma Migrate
-
Empty
dbgenerated()still breaking forUnsupported()types -
Validation error when
shadowDatabaseUrlis identical tourl(ordirectUrl) - MongoDB Query with 'in' condition will cause COLLSCAN, without leveraging indexes
-
"Not Authorised" when directly applying Prisma generated migrations to Cloudflare D1 with
PRAGMA foreign_key_check;
Language tools (e.g. VS Code)
Company news
Prisma Changelog
Curious about all things Prisma? Be sure to check out the Prisma Changelog for updates across Prisma's products, including ORM, Accelerate, and Pulse!
Credits
Huge thanks to @pranayat, @yubrot, @skyzh, @anuraaga, @gutyerrez, @avallete, @ceddy4395, @Kayoshi-dev for helping!
TanStack/query (@tanstack/react-query)
v5.36.2
v5.36.1
Version 5.36.1 - 5/15/2024, 2:22 PM
Changes
Fix
Docs
- not using useState in creating queryClient when use ReactQueryStreamedHydration in suspense-example (#7431) (
3a9e046) by polee
Other
- Update overview.md (
10c7527) by Tanner Linsley
Packages
- @tanstack/query-core@5.36.1
- @tanstack/react-query@5.36.1
- @tanstack/solid-query@5.36.1
- @tanstack/vue-query@5.36.1
- @tanstack/angular-query-experimental@5.36.1
- @tanstack/query-broadcast-client-experimental@5.36.1
- @tanstack/query-persist-client-core@5.36.1
- @tanstack/query-sync-storage-persister@5.36.1
- @tanstack/react-query-devtools@5.36.1
- @tanstack/react-query-persist-client@5.36.1
- @tanstack/react-query-next-experimental@5.36.1
- @tanstack/solid-query-devtools@5.36.1
- @tanstack/solid-query-persist-client@5.36.1
- @tanstack/svelte-query@5.36.1
- @tanstack/svelte-query-devtools@5.36.1
- @tanstack/svelte-query-persist-client@5.36.1
- @tanstack/vue-query-devtools@5.36.1
- @tanstack/angular-query-devtools-experimental@5.36.1
- @tanstack/query-async-storage-persister@5.36.1
v5.36.0
v5.35.5
v5.35.4
Version 5.35.4 - 5/10/2024, 2:10 PM
Changes
Fix
Docs
- Fix usage of removeEventListener (#7393) (
0bb0fa3) by Oc1S - fix typo (#7400) (
ab126e8) by @pius712
Packages
- @tanstack/query-core@5.35.4
- @tanstack/query-broadcast-client-experimental@5.35.4
- @tanstack/query-persist-client-core@5.35.4
- @tanstack/query-sync-storage-persister@5.35.4
- @tanstack/react-query@5.35.4
- @tanstack/react-query-devtools@5.35.4
- @tanstack/react-query-persist-client@5.35.4
- @tanstack/react-query-next-experimental@5.35.4
- @tanstack/solid-query@5.35.4
- @tanstack/solid-query-devtools@5.35.4
- @tanstack/solid-query-persist-client@5.35.4
- @tanstack/svelte-query@5.35.4
- @tanstack/svelte-query-devtools@5.35.4
- @tanstack/svelte-query-persist-client@5.35.4
- @tanstack/vue-query@5.35.4
- @tanstack/vue-query-devtools@5.35.4
- @tanstack/angular-query-experimental@5.35.4
- @tanstack/query-async-storage-persister@5.35.4
- @tanstack/angular-query-devtools-experimental@5.35.4
TanStack/table (@tanstack/react-table)
v8.17.3
Version 8.17.3 - 5/14/2024, 2:44 PM
Changes
Fix
- Add a missing guard for undefined in the getFilteredRowModel function. (#5555) (
5411f1a) by @jjh2613
Packages
- @tanstack/table-core@8.17.3
- @tanstack/qwik-table@8.17.3
- @tanstack/react-table@8.17.3
- @tanstack/solid-table@8.17.3
- @tanstack/vue-table@8.17.3
- @tanstack/svelte-table@8.17.3
- @tanstack/react-table-devtools@8.17.3
- @tanstack/angular-table@8.17.3
v8.17.0
Version 8.17.0 - 5/12/2024, 7:21 PM
Changes
Feat
Chore
Docs
- example code of Deep Keys in column-deps (#5547) (
c1085a6) by taro - Document getAutoFilterFn in column-filtering.md (#5510) (
b1d29b4) by @geryogam - Update tables.md (#5534) (
58f7991) by @naughton - update column defs page title (
eae4d0f) by Kevin Vandy - update overview (
b803962) by Kevin Vandy - header and column docs (#5531) (
102ffd2) by Kevin Van Cott - rename data guide (
64ef24c) by Kevin Vandy - fix links (
ec1ab03) by Kevin Vandy - data and header group docs (#5526) (
72ab26a) by Kevin Van Cott - create cells guide (#5523) (
e80b802) by Kevin Van Cott - rows guide (#5515) (
c7c4419) by Kevin Van Cott - typos in pagination.md (#5508) (
ed37903) by @geryogam - typos in column-filtering.md (#5509) (
2afa14b) by @geryogam - start faceting docs and filter example reorg (#5507) (
289eca3) by Kevin Van Cott - docs pages are breaking due to diff in markdown (#5503) (
365e0e9) by @KushagraMehta
Other
Packages
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.9.0
🩹 Fixes
- eslint-plugin: [explicit-function-return-types] fix false positive on default parameters
❤️ Thank You
- Kirk Waiblinger
- Sheetal Nandi
- Vinccool96
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.9.0
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
hashicorp/terraform-provider-aws (aws)
v5.49.0
FEATURES:
-
New Data Source:
aws_datazone_environment_blueprint(#36600) -
New Resource:
aws_bedrockagent_data_source(#37158) -
New Resource:
aws_datazone_domain(#36600) -
New Resource:
aws_datazone_environment_blueprint_configuration(#36600)
ENHANCEMENTS:
- data-source/aws_iam_policy_document: Add
minified_jsonattribute (#35677) - resource/aws_dynamodb_table_export: Add plan-time validation of
table_arn(#37288) - resource/aws_kms_key: Add
rotation_period_in_daysargument (#37140) - resource/aws_securitylake_subscriber_notification: Better handles importing resource (#37332)
- resource/aws_securitylake_subscriber_notification: Deprecates
endpoint_idin favor ofsubscriber_endpoint(#37332) - resource/aws_securitylake_subscriber_notification: Handles
configuration.https_notification_configuration.authorization_api_key_valueas sensitive value (#37332)
BUG FIXES:
- data-source/aws_fsx_ontap_storage_virtual_machine: Correctly set
tagson Read (#37353) - data-source/aws_rds_orderable_db_instance: Fix
InvalidParameterValue: Invalid value 3412 for MaxRecords. Must be between 20 and 1000errors (#37251) - data-source/aws_resourceexplorer2_search: Fix 401 unauthorized error due to missing
view_arnin the AWS API request (#36778) - data-source/aws_resourceexplorer2_search: Fix panic caused by bad mappping between Terraform and AWS schemas (#36778)
- data-source/aws_resourceexplorer2_search: Fix state persistence and data types (#36778)
- resource/aws_bedrockagent_agent: Fix to use the configured
prepare_agentvalue (or default value oftruewhen omitted) for all create and update operations (#37405) - resource/aws_elasticsearch_domain: Fix handling of unset
auto_tune_options.rollback_on_disableargument (#37394) - resource/aws_fsx_ontap_storage_virtual_machine: Correctly set
tagsandtags_allon resource Read ([#37353](https://togithub.com/hashicorp/terraform-provi
Configuration
📅 Schedule: Branch creation - "before 4am 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.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated (UTC) |
|---|---|---|---|
| codedang | ✅ Ready (Inspect) | Visit Preview | May 27, 2024 0:10am |