-
Notifications
You must be signed in to change notification settings - Fork 579
fix(deps): update all non-major dependencies #4150
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
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-yoga/graphiql |
4.4.1-alpha-20250828022208-da9dca3780469c7631eee5484a02d306bab2f110 |
npm ↗︎ unpkg ↗︎ |
@graphql-yoga/plugin-apollo-usage-report |
0.10.2-alpha-20250828022208-da9dca3780469c7631eee5484a02d306bab2f110 |
npm ↗︎ unpkg ↗︎ |
Apollo Federation Subgraph Compatibility Results
Learn more: |
💻 Website PreviewThe latest changes are available as preview in: https://pr-4150.graphql-yoga.pages.dev |
✅ Benchmark Results
|
7f04b57
to
6a8cfac
Compare
6a8cfac
to
fc432af
Compare
fc432af
to
6479721
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
3.13.9
->3.14.0
7.28.0
->7.28.3
7.28.0
->7.28.3
4.20250807.0
->4.20250826.0
3.1.6
->3.1.7
21.4.2
->21.4.3
4.6.0
->4.6.3
4.8.1
->4.9.0
6.13.0
->6.15.0
6.13.0
->6.15.0
6.13.0
->6.15.0
7.3.1
->7.6.0
1.31.0
->1.32.0
3.6.1
->3.7.1
4.8.0
->4.8.2
3.188.0
->3.191.0
6.0.2
->6.1.0
6.1.1
->6.1.3
24.2.0
->24.3.0
19.1.9
->19.1.12
19.1.7
->19.1.8
2.1024.0
->2.1027.0
2.210.0
->2.212.0
9.2.0
->9.2.1
0.25.8
->0.25.9
9.32.0
->9.34.0
5.4.0
->5.5.0
30.0.5
->30.1.1
16.1.4
->16.1.5
10.14.0
->10.15.0
6.13.0
->6.15.0
5.38.0
->5.38.6
9.5.2
->9.5.4
4.20.3
->4.20.5
7.1.1
->7.1.3
5.101.0
->5.101.3
4.28.1
->4.33.0
Release Notes
apollographql/apollo-client (@apollo/client)
v3.14.0
Compare Source
Minor Changes
#12752
8b779b4
Thanks @jerelmiller! - Add deprecations and warnings to remaining APIs changed in Apollo Client 4.0.#12746
0bcd2f4
Thanks @jerelmiller! - Add warnings and deprecations for options and methods for all React APIs.#12751
567cad8
Thanks @jerelmiller! - Add@deprecated
tags to all properties returned from any query API (e.g.client.query
,observableQuery.refetch
, etc.),client.mutate
, andclient.subscribe
that are no longer available in Apollo Client 4.0.#12746
0bcd2f4
Thanks @jerelmiller! - AddpreloadQuery.toPromise(queryRef)
as a replacement forqueryRef.toPromise()
.queryRef.toPromise()
has been removed in Apollo Client 4.0 in favor ofpreloadQuery.toPromise
and is now considered deprecated.#12736
ea89440
Thanks @jerelmiller! - Add deprecations and deprecation warnings forApolloClient
options and methods.#12763
5de6a3d
Thanks @jerelmiller! - Version bump only to release latest asrc
.#12459
1c5a031
Thanks @jerelmiller! - ResetaddTypenameTransform
andfragments
caches when callingcache.gc()
only whenresetResultCache
istrue
.#12743
92ad409
Thanks @jerelmiller! - Add deprecations and warnings foraddTypename
inInMemoryCache
andMockedProvider
.#12743
92ad409
Thanks @jerelmiller! - Add deprecations and warnings forcanonizeResults
.#12751
567cad8
Thanks @jerelmiller! - Warn when using astandby
fetch policy withclient.query
.Patch Changes
ecf3de1
Thanks @phryneas! - Prevent field policies from overwriting/merging into supertype field policies.babel/babel (@babel/core)
v7.28.3
Compare Source
👓 Spec Compliance
babel-helper-create-class-features-plugin
,babel-plugin-proposal-decorators
,babel-plugin-transform-class-static-block
,babel-preset-env
🐛 Bug Fix
babel-parser
import("./a", {with:{},})
(@easrng)💅 Polish
babel-plugin-transform-regenerator
,babel-plugin-transform-runtime
📝 Documentation
🏠 Internal
scripts
andbabel-worker.cjs
(@JLHwung)🔬 Output optimization
babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-do-expressions
cloudflare/workerd (@cloudflare/workers-types)
v4.20250826.0
Compare Source
v4.20250823.0
Compare Source
v4.20250822.0
Compare Source
v4.20250821.0
Compare Source
v4.20250820.0
Compare Source
v4.20250819.0
Compare Source
v4.20250816.0
Compare Source
v4.20250813.0
Compare Source
v4.20250812.0
Compare Source
v4.20250810.0
Compare Source
v4.20250809.0
Compare Source
Escape-Technologies/graphql-armor (@escape.tech/graphql-armor)
v3.1.7
Compare Source
Patch Changes
9989861
]1f923bc
]hapijs/hapi (@hapi/hapi)
v21.4.3
Compare Source
ianvs/prettier-plugin-sort-imports (@ianvs/prettier-plugin-sort-imports)
v4.6.3
Compare Source
What's Changed
Full Changelog: IanVS/prettier-plugin-sort-imports@4.6.2...v4.6.3
v4.6.2
Compare Source
What's Changed
New Contributors
Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.1...4.6.2
v4.6.1
Compare Source
What's Changed
Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.0...v4.6.1
hayes/pothos (@pothos/core)
v4.9.0
Compare Source
Minor Changes
689accd
: Fix arg mapping for nested listsprisma/prisma (@prisma/client)
v6.15.0
Compare Source
Today, we are excited to share the
6.15.0
stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
AI safety guardrails for destructive commands
Prisma ORM now includes built-in safety checks that protect against destructive commands when triggered by AI coding assistants. The CLI can recognize when it is being executed by popular AI agents such as Claude Code, Gemini CLI, Qwen Code, Cursor, Aider and Replit.
If a command like
prisma migrate reset --force
is attempted, Prisma ORM will prompt for explicit confirmation before proceeding.This feature ensures that irreversible operations which drop and recreate the database are not executed automatically by an AI tool. Prisma ORM is the first ORM to provide this level of protection, making it safer to use AI-assisted development while working with your databases.
📚 Learn more in the docs.
prisma-client
: runtime improvements and schema flexibilityWe simplified Prisma ORM by making the runtime options for the Prisma Client more consistent and easier to understand. Previously there were several overlapping aliases which created confusion. With this release we simplified the inputs while keeping support for all the major environments you might be targeting.
Changes include:
node
has been removed, useruntime = "nodejs"
insteaddeno-deploy
has been removed, useruntime = "deno"
insteadvercel
has been replaced by the newruntime = "vercel-edge"
edge-light
is now just an alias forvercel-edge
nodejs
,deno
, andbun
now share the same internal code path, while still keeping their separate input values for clarityThe updated list of supported runtimes is now:
nodejs
,deno
,bun
,workerd
(aliascloudflare
),vercel-edge
(aliasedge-light
), andreact-native
.In addition, we fixed an issue where running
prisma generate
would fail if your schema contained no models. This is now supported with the newprisma-client
generator, just like it already worked with the olderprisma-client-js
generator.For example, the following schema will now generate a client without errors:
Running
prisma generate
with this schema will succeed and create the client in./generated/client
.📚 Learn more in the docs.
Using Prisma ORM with Vercel Fluid
Fluid compute is a new compute model from Vercel that combines the flexibility of serverless with the stability of servers, making it ideal for dynamic workloads such as streaming data and AI APIs.
A common challenge in traditional serverless platforms is that when functions are suspended, database connection pools can’t close idle connections. This leads to leaked connections that stay open until the database times them out, which can exhaust the pool.
Vercel provides the
attachDatabasePool
utility to solve this problem. It ensures idle connections in the pool are properly released before a function is suspended, preventing connection leaks.You can use this utility together with Prisma’s driver adapters to safely manage database connections in Fluid Compute:
📚 Learn more in the docs.
Other news
Prisma Postgres Management API is Generally Available
The Prisma Postgres Management API allows you to programmatically provision and manage Prisma Postgres instances. It’s the perfect way to spin up a database in your CI/CD workflow, see our GitHub Action examples for creating and deleting if you’re curious about this use case.
It also enables developers to offer databases to their own users! For example, did you know that Co.dev (YC23), a popular “low-code AI app builder” is using the Management API to provision Prisma Postgres instances to people building apps with their platform?
We’re excited to share that the Management API is now fully ready for production. With it moving into GA, we also added another piece of functionality where you can now create new projects without a default database.
We’re looking forward to see what you’re going to build with it!
📚 Learn more in the docs.
Prisma Postgres is now available on Pipedream
Prisma Postgres can now be used directly in your Pipedream workflows 🎉
With this integration, you can connect Prisma Postgres to over 2,800+ apps supported on Pipedream, enabling powerful automations and data workflows. For example, you can:
This makes it easier than ever to use Prisma Postgres in your automation pipelines, without needing to manage custom scripts or infrastructure.
📚 Learn more on the Pipedream integration page.
New
--json
flag fornpx create-db
The
npx create-db
command lets you spin up a temporary, production-ready Prisma Postgres database that you can later claim for continued use. With this release, you can now add the--json
flag to return the database details in JSON format.This makes it straightforward to programmatically use the connection details, whether you are building custom APIs or integrating database provisioning into your workflows.
📚 Learn more in the docs.
Direct connections to Prisma Postgres are coming close to GA
Direct connections enable you to connect to your database using any ORM library or tool of your choice (e.g. Drizzle ORM, Kysely but also database GUIs like Postico or TablePlus).
In this release, we’ve improved the robustness of direct TCP connections and are close to bringing it to General Availability.
📚 Learn more in the docs.
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.14.0
Compare Source
Today, we are excited to share the
6.14.0
stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
@unique
attributes for SQL views (Preview)Last release, we improved the robustness of SQL views defined in the Prisma schema. Views are virtual tables that don't allows for defining unique constraints, indexes or foreign keys in the underlying database.
However, as an application developer, it can be convenient to also define relationships involving views or paginate them using cursors. We've received this feedback from several people who had been using views in that way with Prisma ORM, so in this release we're re-introducing the
@unique
attribute for views. This attribute enables:findUnique
queries, cursor-based pagination & implicit ordering for viewsHere's an example schema using
@unique
and defining a relationship from a model to a view:Expand to view the SQL code for this view
You can now query this view and its relationship using
include
:📚 Learn more in the docs.
Various fixes & stability improvements
prisma-client
generator and thequeryCompiler
Preview feature (aka “Prisma Client without Rust engines”). Both will become the default in the upcoming Prisma 7 release and we're working hard on bringing these features into General Availability. You can try them out with your favorite stack with our ready-to-run examples.prisma.$use
method), which was deprecated since v4.16.0. Use Prisma Client extensions instead.metrics
Preview feature (which will be removed in Prisma 7)Improved type performance
In this release, we also addressed some type performance issues that led to slower editors and lagging auto-complete. If you're curious about the details, you can check the description and changes in this PR.
Other news
Increased robustness of Management API (Early Access)
We recently released an API for programmatically managing Prisma Postgres instances that's perfect for CI/CD workflows and scripting.
In this release, we made it more robust and are bringing it closer to its General Availability release.
Revoke OAuth tokens in Prisma Console
If you use OAuth to authorize third-party applications to act on your behalf in the Prisma Console, you can now revoke any app's access at any time. The Prisma Console shows a list of your authorized (connected) apps, and you can easily remove one to immediately block further access.
Big fixes in Prisma Console
ICYMI
Last release was huge, so just in case you missed it, here's the TLDR of what we put out last time:
prisma.config.ts
) is Generally Available – Native way to configure schema paths, migrations, seeds, and more; no need forearlyAccess
flag anymore.@@​schema
.pgvector
,pg_search
,pg_stat_statements
,citext
,pg_trgm
,fuzzystrmatch
, andunaccent
. If you don't see the extension you need, you can request it here. Extensions only work on new instances, if you want to use any of them on your existing instance, reach out to us.npx create-db
– Instantly spin up a new Postgres database—no authentication required.pulumi/pulumi-aws (@pulumi/aws)
v7.6.0
Compare Source
What's Changed
Full Changelog: pulumi/pulumi-aws@v7.5.0...v7.6.0
v7.5.0
Compare Source
What's Changed
Full Changelog: pulumi/pulumi-aws@v7.4.0...v7.5.0
v7.4.0
Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
New resources:
networkfirewall/vpcEndpointAssociation.VpcEndpointAssociation
quicksight/customPermissions.CustomPermissions
quicksight/roleCustomPermission.RoleCustomPermission
quicksight/userCustomPermission.UserCustomPermission
wafv2/webAclRuleGroupAssociation.WebAclRuleGroupAssociation
What's Changed
Full Changelog: pulumi/pulumi-aws@v7.3.1...v7.4.0
pulumi/pulumi-aws-native (@pulumi/aws-native)
v1.32.0
Compare Source
pulumi/pulumi-azure-native (@pulumi/azure-native)
v3.7.1
Compare Source
Does the PR have any schema changes?
Found 5 breaking changes:
Types
🟢
"azure-native:app:BlobStorageTokenStore": required: "sasUrlSettingName" property is no longer Required🟢
"azure-native:app:BlobStorageTokenStoreResponse": required: "sasUrlSettingName" property is no longer Required🟢
"azure-native:app:CertificateResponseProperties": required: "deploymentErrors" property has changed to Required🟢
"deploymentErrors" property has changed to Required🟢
"provisioningState" property has changed to RequiredNo new resources/functions.
What's Changed
Full Changelog: pulumi/pulumi-azure-native@v3.7.0...v3.7.1
v3.7.0
Compare Source
Does the PR have any schema changes?
Found 3 breaking changes:
Resources
🟢
"azure-native:botservice:Bot": required: "location" property is no longer Required🟢
"azure-native:botservice:Channel": required: "location" property is no longer Required🟢
"azure-native:maintenance:MaintenanceConfiguration": required: "location" property is no longer RequiredNew resources:
containerservice.IdentityBinding
fileshares.FileShare
mission.Approval
mission.Community
mission.CommunityEndpoint
mission.EnclaveConnection
mission.EnclaveEndpoint
mission.TransitHub
mission.VirtualEnclave
mission.Workload
security.PrivateEndpointConnection
security.PrivateLink
New functions:
containerservice.getIdentityBinding
fileshares.getFileShare
fileshares.getFileShareLimits
fileshares.getFileShareProvisioningRecommendation
fileshares.getFileShareUsageData
mission.getApproval
mission.getCommunity
mission.getCommunityEndpoint
mission.getEnclaveConnection
mission.getEnclaveEndpoint
mission.getTransitHub
mission.getVirtualEnclave
mission.getWorkload
security.getPrivateEndpointConnection
security.getPrivateLink
What's Changed
New Contributors
Full Changelog: pulumi/pulumi-azure-native@v3.6.1...v3.7.0
pulumi/pulumi-docker (@pulumi/docker)
v4.8.2
Compare Source
What's Changed
Full Changelog: pulumi/pulumi-docker@v4.8.1...v4.8.2
v4.8.1
Compare Source
What's Changed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.