chore(deps): update dependency relay-runtime to v21#58
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
March 24, 2021 14:52
12af33c to
e6b4d61
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
2 times, most recently
from
April 15, 2021 19:25
7b9cd45 to
52a40e8
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
May 10, 2021 04:20
52a40e8 to
cf85666
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
2 times, most recently
from
June 7, 2021 02:08
51d28d0 to
b1b71cb
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
2 times, most recently
from
June 28, 2021 02:00
d1e538b to
127823f
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
October 19, 2021 02:35
127823f to
2b38c16
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
March 7, 2022 08:54
2b38c16 to
ec4a983
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
March 26, 2022 12:03
ec4a983 to
4800b11
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
June 8, 2022 19:05
4800b11 to
73d4d33
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
September 25, 2022 18:59
73d4d33 to
2ab6849
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
November 20, 2022 17:25
2ab6849 to
de57053
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
March 16, 2023 08:03
de57053 to
9f5c927
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
October 19, 2023 21:19
9f5c927 to
4a35611
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
December 11, 2023 22:32
4a35611 to
7c28968
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
January 23, 2024 20:13
7c28968 to
ef1d3ef
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
June 15, 2024 00:32
ef1d3ef to
f3cc104
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
September 7, 2024 04:07
f3cc104 to
ffd2aaf
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
October 4, 2024 21:34
ffd2aaf to
cfd9fe7
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
November 21, 2024 23:26
cfd9fe7 to
fdebbae
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
May 2, 2025 22:47
fdebbae to
c1c6e93
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
June 14, 2025 06:34
c1c6e93 to
ef5c22e
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
July 28, 2025 19:42
ef5c22e to
3b2d1b2
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
August 7, 2025 01:40
3b2d1b2 to
50a17cc
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
August 19, 2025 15:10
50a17cc to
6814dcf
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
September 25, 2025 16:09
6814dcf to
24a69fd
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
January 19, 2026 16:49
24a69fd to
1317fdd
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
March 27, 2026 13:14
1317fdd to
68dcd02
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
May 18, 2026 23:30
68dcd02 to
0d0b4a6
Compare
renovate
Bot
force-pushed
the
renovate/major-relay-monorepo
branch
from
May 27, 2026 19:31
0d0b4a6 to
33c505e
Compare
This file contains hidden or 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
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:
^10.1.3→^21.0.1Release Notes
facebook/relay (relay-runtime)
v21.0.1Compare Source
Version 21.0.0 had an issue where it failed to include our new TypeScript types in the published NPM bundle. Thanks to @PHILLIPS71 for the pull request identifying and resolving the issue. This point release resolves that issue and includes a number of other minor improvements which have landed since to v21.0.0 release.
Bug fixes
Added
Improvements
shard_extra_artifactsfeature flag to shard PHP text artifacts by Tianyu Yao (commit)Documentation Improvements
Miscellaneous
v21.0.0Compare Source
Relay v21.0.0 brings first-party TypeScript support, modernized Flow type generation, new error handling capabilities, and experimental React Server Components support. This release contains several breaking changes -- please read the migration notes below carefully.
Upgrading
TypeScript users: First-party
.d.tstype definitions are now shipped directly inrelay-runtimeandreact-relay. You no longer need@types/relay-runtimefrom DefinitelyTyped. Node.js ESM named imports (e.g.import { fetchQuery } from 'relay-runtime') now work correctly in.mjsfiles. Thank you to everyone who contributed to the DefinitelyTyped type definitions over the years — your work kept the Relay TypeScript community going, and it served as a valuable reference for these first-party types.Flow users -- action required: Generated types now use modern Flow syntax.
(expr: Type)casts are replaced with(expr as Type)(requires Flow >= 0.250.0),$ReadOnlyArraybecomesReadonlyArray,mixedbecomesunknown, and$NonMaybeTypebecomesNonNullable. After upgrading, you must re-run the Relay compiler to regenerate all artifacts.@live_queryremoved: The@live_querydirective has been removed. Migrate to@client_polling(interval: ...)for polling behavior, or@livefor server-pushed updates.Relay Resolvers -- new syntax required: The
enable_legacy_verbose_resolver_syntaxflag has been removed. The legacy verbose docblock syntax (@onType,@onInterface,@fieldName,@edgeTo) no longer works. In addition, we've replaced the generic@RelayResolvertag with more specific@relayFieldand@relayTypetags. The Relay compiler can automatically migrate you to this new syntax via therelay-compiler codemod fix-allcommand. If you're not ready to migrate, you can enable theallow_legacy_relay_resolver_tagfeature flag in your compiler config file.@oneOfinputs:@oneOfinput types now generate a stricter discriminated union type that only permits one property at a time, instead of an object with all optional fields. This catches bugs at compile time where multiple fields were incorrectly set simultaneously. You can opt out viaoneOfType: "relaxed"in compiler config if needed.New Features
@catchexpansion:@catchnow works on@connectionfields and client edge fields, letting you gracefully handle field errors in pagination and client-edge scenarios instead of throwing.@aliason fragment definitions: The@aliasdirective now works on fragment definitions (not just inline fragments).New compiler CLI tools: Two experimental subcommands are available:
experimental-regenerate-sub-schemareplaces the currently configured schema file with the portion of the provided "full schema" andexperimental-compare-document-ircompares intermediate representations (IR) of documents passed and outputs selections that exists in left but not in right.React Server Components (Experimental): A new
react-relay/rsc_EXPERIMENTALentry point provides an experimental API for fetching GraphQL in server components:serverFetchQueryfor server-side data fetching,serverReadFragmentfor reading fragment data on the server, andserverPreloadQuery+useQueryFromServerfor preloading data on the server and hydrating the client store. These APIs are experimental and are likely to change in upcoming versions.Notable Bug Fixes
@raw_response_typeaccuracy: Selections on abstract types in@raw_response_typeare now correctly typed as optional when the concrete type may not implement the abstract type (PR #4775).@matchfields: The compiler now properly validates and reports errors for conflicting@matchfields across fragments, preventing silent runtime issues.--watchmode, including cross-project fragment crash resolution and proper detection of schema field changes.Breaking Changes
mixedtounknown(commit)Added
query-statssubcommand for per-operation fragment usage analysis (commit)Bug Fixes
<Activity>a->b->a mutation edge case (commit)Improvements
extend X { ... }instead ofX { ... }(commit)react-prefer-namespace-importESLint Rule (commit)requireCond(commit)prettycrate for document-based formatting (commit)set_remove_defined_referencesto remove Set contents from a given exclusionary schema (commit)arc lint --take PRETTIERJAVASCRIPT(commit)$ValuestoValues(commit)mixedtounknownin xplat/js (commit)$NonMaybeType) to TypeScript-style types in xplat/js (commit)Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 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.