-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update Patch Dependencies #603
Merged
Merged
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
2590956
to
abddefb
Compare
abddefb
to
3ada3e7
Compare
3ada3e7
to
cbdaf0a
Compare
cbdaf0a
to
7d2c174
Compare
7d2c174
to
dc6826b
Compare
dc6826b
to
008cd21
Compare
008cd21
to
4b54e08
Compare
4b54e08
to
50ad931
Compare
50ad931
to
8acc685
Compare
8acc685
to
9326c4d
Compare
9326c4d
to
3f4a2da
Compare
3f4a2da
to
8107b0a
Compare
8107b0a
to
7fbd48b
Compare
7fbd48b
to
846ff1f
Compare
b0eb780
to
d15160a
Compare
d15160a
to
fb2d9fb
Compare
fb2d9fb
to
7daf494
Compare
7daf494
to
b38ddbb
Compare
b38ddbb
to
51777c6
Compare
51777c6
to
d2a3fe5
Compare
d2a3fe5
to
0e40bd0
Compare
0e40bd0
to
9f9e944
Compare
Deployment failed with the following error:
|
ff0e1b6
to
21b0c1d
Compare
21b0c1d
to
9b10867
Compare
9b10867
to
a88854d
Compare
a88854d
to
d93c02a
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:
1.0.9
->1.0.13
^1.1.0
->^1.1.9
^3.12.4
->^3.12.10
^1.2.4
->^1.2.6
^15.1.3
->^15.1.6
^6.3.0
->^6.3.1
6.3.0
->6.3.1
6.3.0
->6.3.1
6.3.0
->6.3.1
^1.1.2
->^1.1.3
^1.1.4
->^1.1.6
^1.1.4
->^1.1.6
^1.1.1
->^1.1.2
^0.5.9
->^0.5.10
^0.5.15
->^0.5.16
^4.17.14
->^4.17.15
^22.13.0
->^22.13.1
^19.0.2
->^19.0.8
^19.0.2
->^19.0.3
^8.5.13
->^8.5.14
^0.27.0
->^0.27.1
^0.10.1
->^0.10.3
^4.1.0
->^4.1.24
^1.25.0
->^1.25.3
^8.17.1
->^8.17.3
15.1.3
->15.1.6
^3.31.0
->^3.31.4
^15.1.3
->^15.1.6
10.2.0
->10.2.1
^0.6.9
->^0.6.11
6.3.0
->6.3.1
^9.5.0
->^9.5.1
^5.7.2
->^5.7.3
Release Notes
0no-co/graphql.web (@0no-co/graphql.web)
v1.0.13
Compare Source
Patch Changes
Submitted by @andreisergiu98 (See #49)
v1.0.12
Compare Source
Patch Changes
Submitted by @JoviDeCroock (See #46)
v1.0.11
Patch Changes
Submitted by @jaulz (See #36)
v1.0.10
Patch Changes
loc
getter to parsedDocumentNode
fragment outputs to ensure that using fragments created bygql.tada
'sgraphql()
function withgraphql-tag
doesn't crash.graphql-tag
does not treat theDocumentNode.loc
property as optional on interpolations, which leads to intercompatibility issuesSubmitted by @JoviDeCroock (See #38)
Submitted by @JoviDeCroock (See #39)
vercel/ai (@ai-sdk/openai)
v1.1.9
Compare Source
Patch Changes
c55b81a
: fix (provider/openai): fix o3-mini streamingv1.1.8
Compare Source
Patch Changes
161be90
: fix (provider/openai): fix model id typov1.1.7
Compare Source
Patch Changes
0a2f026
: feat (provider/openai): add o3-miniv1.1.6
Compare Source
Patch Changes
d89c3b9
: feat (provider): add image model support to provider specificationd89c3b9
]v1.1.5
Compare Source
Patch Changes
3a602ca
]v1.1.4
Compare Source
Patch Changes
066206e
]v1.1.3
Compare Source
Patch Changes
39e5c1f
]v1.1.2
Compare Source
Patch Changes
ed012d2
]3a58a2e
]v1.1.1
Compare Source
Patch Changes
858f934
: feat (provider/anthropic): default cache-control on and mark model setting deprecatedb284e2c
: feat (provider/google-vertex): support prompt caching for Anthropic Claude modelse7a9ec9
]0a699f1
]apollographql/apollo-client (@apollo/client)
v3.12.10
Compare Source
Patch Changes
#12341
f2bb0b9
Thanks @phryneas! -useReadQuery
/useQueryRefHandlers
: Fix a "hook order" warning that might be emitted in React 19 dev mode.#12342
219b26b
Thanks @phryneas! - Addgraphql-ws
^6.0.3
as a validpeerDependency
v3.12.9
Compare Source
Patch Changes
#12321
daa4f33
Thanks @jerelmiller! - Fix type ofextensions
inprotocolErrors
forApolloError
and theonError
link. According to the multipart HTTP subscription protocol, fatal tranport errors follow the GraphQL error format which requireextensions
to be a map as its value instead of an array.#12318
b17968b
Thanks @jerelmiller! - AllowRetryLink
to retry an operation when fatal transport-level errors are emitted from multipart subscriptions.v3.12.8
Compare Source
Patch Changes
#12292
3abd944
Thanks @phryneas! - Remove unused dependencyresponse-iterator
#12287
bf313a3
Thanks @phryneas! - Fixes an issue whereclient.watchFragment
/useFragment
with@includes
crashes when a separate cache update writes to the conditionally included fields.v3.12.7
Compare Source
Patch Changes
#12281
d638ec3
Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with theprotocolErrors
property.#12281
d638ec3
Thanks @jerelmiller! - Fix the array type for theerrors
field on theApolloPayloadResult
type. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.v3.12.6
Compare Source
Patch Changes
#12267
d57429d
Thanks @jerelmiller! - Maintain theTData
type when used withUnmasked
whenTData
is not a masked type generated from GraphQL Codegen.#12270
3601246
Thanks @jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values withUnmasked
.v3.12.5
Compare Source
Patch Changes
#12252
cb9cd4e
Thanks @jerelmiller! - Changes the default behavior of theMaybeMasked
type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.A new
mode
option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.Migrating from <= v3.12.4
If you've adopted data masking and have opted in to using masked types by setting the
enabled
property totrue
, you can remove this configuration entirely:If you prefer to specify the behavior explicitly, change the property from
enabled: true
, tomode: "preserveTypes"
:If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the
mode
tounmask
:eslint/rewrite (@eslint/compat)
v1.2.6
Compare Source
v1.2.5
Compare Source
vercel/next.js (@next/eslint-plugin-next)
v15.1.6
Compare Source
Core Changes
Credits
Huge thanks to @lubieowoce and @ztanner for helping!
v15.1.5
Compare Source
Core Changes
Credits
Huge thanks to @ijjk, @huozhi, @matmannion and @ztanner for helping!
v15.1.4
Compare Source
Core Changes
Credits
Huge thanks to @ and @ for helping!
prisma/prisma (@prisma/adapter-neon)
v6.3.1
Compare Source
This patch releases introduces improvements to the
prisma init
output when invoked to with the--db
option.Run
npx prisma@latest init --db
to get an instant Prisma Postgres database.radix-ui/primitives (@radix-ui/react-avatar)
v1.1.3
Compare Source
tailwindlabs/tailwindcss-forms (@tailwindcss/forms)
v0.5.10
Compare Source
Fixed
tailwindlabs/tailwindcss-typography (@tailwindcss/typography)
v0.5.16
Compare Source
Fixed
vercel/storage (@vercel/blob)
v0.27.1
Compare Source
Patch Changes
0c98feb
: fix(blob): allow client uploads in web workersBefore this change, we had guards so client uploads could only be used in
browser environments, this prevented customers to use Vercel Blob in Web
Workers, sometimes React Native or in general anywhere window is not really what
we think it is.
ardatan/whatwg-node (@whatwg-node/fetch)
v0.10.3
Compare Source
Patch Changes
2785c80
Thanks @ardatan! -
ReadableStream
'sSymbol.asyncIterator
nowreturns
AsyncIterableIterator
like before even if it is ok to returnAsyncIterator
right now.It is safer to return
AsyncIterableIterator
because it is a common mistake to useAsyncIterator
asAsyncIterable
.[
2785c80
]:v0.10.2
Compare Source
Patch Changes
b88b85c
Thanks @ardatan! - dependencies updates:
@whatwg-node/node-fetch@^0.7.5
↗︎(from
^0.7.1
, independencies
)[
b88b85c
,9b39c3e
,b88b85c
]:awslabs/aws-crt-nodejs (aws-crt)
v1.25.3
Compare Source
What's Changed
Full Changelog: awslabs/aws-crt-nodejs@v1.25.2...v1.25.3
v1.25.2
: Fix segfaults -- CRC64NVME on machines with disabled AVX and uri parsing corner case.Compare Source
What's Changed
Full Changelog: awslabs/aws-crt-nodejs@v1.25.1...v1.25.2
v1.25.1
: Fix memory leak during signingCompare Source
What's Changed
Full Changelog: awslabs/aws-crt-nodejs@v1.25.0...v1.25.1
streetsidesoftware/cspell (cspell)
v8.17.3
Compare Source
v8.17.2
Compare Source
inngest/inngest-js (inngest)
v3.31.4
Compare Source
Patch Changes
b304e1c
Thanks @BrunoScheufler! - - Remove connect from inngest client, split out intoinngest/connect
v3.31.3
Compare Source
Patch Changes
c331190
Thanks @BrunoScheufler! - - Read signing key from env var for connectv3.31.2
Compare Source
Patch Changes
#824
1d72eae
Thanks @BrunoScheufler! - - Handle immediate WebSocket failure when connecting to gateway#822
1136087
Thanks @jpwilliams! - Sending events now has retries, backing off over 5 attemptsv3.31.1
Compare Source
Patch Changes
#817
446be1b
Thanks @jpwilliams! -serve()
andconnect()
now have looser typing forclient
andfunctions
, resulting in easier use of multipleinngest
packages in a single process#823
f1d2385
Thanks @jpwilliams! - Allow wildcard event typing with.fromRecord()
The following schema is now valid:
When creating a function, this allows you to appropriately type narrow the event to pull out the correct data:
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.