-
Notifications
You must be signed in to change notification settings - Fork 1
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 dependency @urql/core to v4.3.0 #34
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/urql-core-4.x-lockfile
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
July 19, 2023 12:11
8b9c74e
to
e283212
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.0.11
fix(deps): update dependency @urql/core to v4.1.0
Jul 21, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
July 21, 2023 16:38
e283212
to
0bf8c9f
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.1.0
fix(deps): update dependency @urql/core to v4.1.1
Jul 30, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
July 30, 2023 18:59
0bf8c9f
to
0f33c12
Compare
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
August 9, 2023 12:53
0f33c12
to
8b28513
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.1.1
fix(deps): update dependency @urql/core to v4.1.2
Aug 31, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
August 31, 2023 18:08
8b28513
to
c312532
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.1.2
fix(deps): update dependency @urql/core to v4.1.3
Sep 18, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
September 18, 2023 22:25
c312532
to
c9734f4
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.1.3
fix(deps): update dependency @urql/core to v4.1.4
Oct 19, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
October 19, 2023 20:25
c9734f4
to
0a10969
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.1.4
fix(deps): update dependency @urql/core to v4.2.0
Nov 14, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
November 14, 2023 22:14
0a10969
to
dffa620
Compare
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
December 10, 2023 19:22
dffa620
to
0fdc7e0
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.2.0
fix(deps): update dependency @urql/core to v4.2.1
Dec 10, 2023
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
December 12, 2023 16:08
0fdc7e0
to
f286ff1
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.2.1
fix(deps): update dependency @urql/core to v4.2.2
Dec 12, 2023
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.2.2
fix(deps): update dependency @urql/core to v4.2.3
Jan 17, 2024
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
January 17, 2024 20:39
f286ff1
to
2c31c17
Compare
renovate
bot
changed the title
fix(deps): update dependency @urql/core to v4.2.3
fix(deps): update dependency @urql/core to v4.3.0
Mar 3, 2024
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
March 3, 2024 13:36
2c31c17
to
63bf26e
Compare
renovate
bot
force-pushed
the
renovate/urql-core-4.x-lockfile
branch
from
June 4, 2024 15:08
63bf26e
to
89505ce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
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.0.10
->4.3.0
Release Notes
urql-graphql/urql (@urql/core)
v4.3.0
Compare Source
Minor Changes
multipart/mixed
responses (result properties essentially are namespaced on apayload
key)Submitted by @JoviDeCroock (See #3499)
DocumentNode
with no/empty definitions and adocumentId
property is considered a persisted document. When this is detected adocumentId
parameter rather than aquery
string is sent to the GraphQL API, similar to Automatic Persisted Queries (APQs). However, APQs are only supported via@urql/exchange-persisted
, while support fordocumentId
is now built-inSubmitted by @kitten (See #3515)
Patch Changes
url
to be a plain, non-URL pathname (i.e./api/graphql
) to be used withpreferGetMethod
Submitted by @akrantz01 (See #3514)
Headers
class being used infetchOptions
Submitted by @JoviDeCroock (See #3505)
v4.2.3
Compare Source
Patch Changes
Submitted by @JoviDeCroock (See #3464)
v4.2.2
Compare Source
Patch Changes
cacheExchange
crashing oncache-only
request policies with cache misses due toundefined
resultsSubmitted by @JoviDeCroock (See #3459)
v4.2.1
Compare Source
Patch Changes
Submitted by @SoraKumo001 (See #3453)
v4.2.0
Compare Source
Minor Changes
text/plain
content-type as JSON before bailing out with an errorSubmitted by @JoviDeCroock (See #3430)
v4.1.4
Compare Source
Patch Changes
@defer
/@stream
transport protocol spec changesSubmitted by @JoviDeCroock (See #3389)
errors
but as an object. Addinga check whether we are really dealing with an Array of errors enables this
Submitted by @JoviDeCroock (See #3395)
preferGetMethod: 'force' | 'within-url-limit'
not being applied correctly by theClient
Submitted by @Burbenog (See #3403)
v4.1.3
Compare Source
Patch Changes
teardown
operation handling in thessrExchange
. This could lead to duplicate network operations being executedSubmitted by @kitten (See #3386)
v4.1.2
Compare Source
Patch Changes
client.reexecuteOperation
calls to allow stalled operations from continuing and re-executing. Previously, this could cause@urql/exchange-graphcache
to stall if an optimistic mutation led to a cache missSubmitted by @kitten (See #3363)
v4.1.1
Compare Source
Patch Changes
subscriptionExchange
to handleGraphQLError[]
received in theerror
observer callback.Note: This doesn't strictly check for the
GraphQLError
shape and only checks for arrays and receiving errors in theExecutionResult
on thenext
observer callback is preferred and recommended for transportsSubmitted by @kitten (See #3346)
v4.1.0
Compare Source
Minor Changes
formatDocument
to outputFormattedNode
type mapping. The formatter will now annotate added__typename
fields with_generated: true
, place selection nodes' directives onto a_directives
dictionary, and will filter directives to not include"_"
underscore prefixed directives in the final query. This prepares us for a feature that allows enhanced client-side directives in GraphcacheSubmitted by @kitten (See #3317)
Patch Changes
OperationContext.optimistic
flag as an internal indication on whether a mutation triggered an optimistic update in@urql/exchange-graphcache
'scacheExchange
Submitted by @kitten (See #3308)
v4.0.11
Compare Source
Patch Changes
maskTypename
to apply masking earlier in the chainSubmitted by @kitten (See #3298)
ssrExchange
not formatting query documents usingformatDocument
. Without this call we'd run the risk of not having__typename
available on the client-side when rehydratingSubmitted by @kitten (See #3288)
maskTypename
option.Masking typenames in a result is no longer recommended. It’s only
useful when multiple pre-conditions are applied and inferior to
mapping to an input object manually
Submitted by @kitten (See #3299)
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.