Relay 20.1.1 #28
Merged
Relay 20.1.1 #28
Conversation
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
Reviewed By: panagosg7 Differential Revision: D72353682 fbshipit-source-id: 72a1551870bc5a0abb7709fac94d442ffa200d89
Reviewed By: SamChou19815 Differential Revision: D72406426 fbshipit-source-id: 8a72ed9b0a0752a6b97bd324525ffdf1123c6619
Reviewed By: tyao1 Differential Revision: D72075980 fbshipit-source-id: 8064eb47f83632c413a86db61453b6a391544e30
Reviewed By: panagosg7 Differential Revision: D72417828 fbshipit-source-id: daa35a4c70bfd5e91ed1592a21c96619f9ebdd22
Reviewed By: SamChou19815 Differential Revision: D72423266 fbshipit-source-id: e6832fb66ffe8c4c548bcbcb23da0788e86f7139
Reviewed By: captbaritone Differential Revision: D72359401 fbshipit-source-id: 41eb6faaa19e9a29dd218898a4e7f278621345aa
Reviewed By: janettec Differential Revision: D72392851 fbshipit-source-id: c5571e922064092f4ac99d0e2b6672454c60df17
Reviewed By: janettec Differential Revision: D72392852 fbshipit-source-id: 9e89e24bcdd45f1ee4dbb730b02ff530c74277d3
Reviewed By: captbaritone Differential Revision: D72573884 fbshipit-source-id: dc44c8a33f2894efb731f7546a7766fc06035b5a
Reviewed By: captbaritone Differential Revision: D72352931 fbshipit-source-id: 88ed7c934767488708feb9453f1bcf4b21c7fdbc
Reviewed By: captbaritone Differential Revision: D72684608 fbshipit-source-id: e9bda6a24af8ea972cea3e27e448ec6213326149
Reviewed By: captbaritone Differential Revision: D72500262 fbshipit-source-id: af3b725fa8d699a31c4d6461c3714dbc29cc10da
Reviewed By: captbaritone Differential Revision: D72726041 fbshipit-source-id: e44f595057f89678e9f42b39d905e891e71647f1
Reviewed By: gkz Differential Revision: D72742388 fbshipit-source-id: f3b65c6cfad97ac268de6756715357ba73f1ea8f
Reviewed By: captbaritone Differential Revision: D72801940 fbshipit-source-id: d7170f6678163d9b075c3f9ce794ef5dc6b97b87
Reviewed By: cyan33 Differential Revision: D72831388 fbshipit-source-id: b11e0b4e9a078b9245a9b89930e4e0ea255d95cc
Reviewed By: gkz Differential Revision: D72879385 fbshipit-source-id: 9b896bf1339116d6d8be78c512ad1efb6a3ea49b
Reviewed By: evanyeung Differential Revision: D72876441 fbshipit-source-id: 7fcbd6c57e4f5e53dc2dee87ded31604a7a950e4
Reviewed By: panagosg7 Differential Revision: D72878876 fbshipit-source-id: 67e67acfa1969fd4039e0c69465e1dc77cce8066
Summary: Fixes >npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/react npm ERR! react@"^19.1.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.9.0 || ^17 || ^18" from [email protected] npm ERR! node_modules/react-relay npm ERR! react-relay@"^18.2.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. Pull Request resolved: facebook#4944 Reviewed By: monicatang Differential Revision: D72893457 Pulled By: tyao1 fbshipit-source-id: d4fadc8f20d949cf7e290bc1835ac23256cb745d
Reviewed By: captbaritone Differential Revision: D72473846 fbshipit-source-id: 8b134c4736dfaa78d6b3a55a3a8a712ca1dce724
Reviewed By: captbaritone Differential Revision: D72816972 fbshipit-source-id: 7ef33c4ae18444df2a7de6b009f502e1798da8f1
Reviewed By: mvitousek Differential Revision: D72888246 fbshipit-source-id: 88aa6dad3a968858a22aaa43a2118aa4a0ec5f82
Reviewed By: robhogan Differential Revision: D72693713 fbshipit-source-id: f529b78a933ae7a6497f67f1f616c1acb95995c3
Reviewed By: capickett Differential Revision: D73041643 fbshipit-source-id: 14092a58e4439d689ff7eea9cfbd9477071809e4
Reviewed By: dtolnay Differential Revision: D73054142 fbshipit-source-id: bd316f8eecf1d1eaba75319f7ab2a67cc06fabbd
Reviewed By: capickett Differential Revision: D73064283 fbshipit-source-id: 89375371d732feb2f0859318081ed64252f448f5
Reviewed By: tyao1 Differential Revision: D73052120 fbshipit-source-id: d5ad211daac173024b194a4003984889a7bb34c5
Reviewed By: dtolnay Differential Revision: D73082326 fbshipit-source-id: 746f2d52cca928403a8f4880ab5f408fd52cdb88
Reviewed By: diliop Differential Revision: D73039734 fbshipit-source-id: f0f7d0ab7a543b6102adfdae0948523bcffc224f
Summary: X-link: meta-pytorch/monarch#635 TSIA Update clap4 4.5.38 -> 4.5.41 Reviewed By: dtolnay Differential Revision: D78907188 fbshipit-source-id: 7c8a7fdb6ee2b512fc767c9ee1248e9e30c667ee
Reviewed By: marcoww6 Differential Revision: D78923286 fbshipit-source-id: fd0b20090a7cd5c5ff64c1dd976e6a8f5e2b59d7
Summary: When a crate that relay uses is updated in the global Cargo.toml we have to regenerate this file.... otherwise you get a task based on an external (a GitHub action) workflow. I forget to do this like 50% of the time. [relay]: Update Cargo.oss.lock Reviewed By: cjlongoria Differential Revision: D78931401 fbshipit-source-id: d60b018333dc21ee71a617435a37cf8ad4570d64
Reviewed By: cjlongoria Differential Revision: D78949285 fbshipit-source-id: 1147c6b3783f9eb0e292a962b698a2c79b50c07a
Reviewed By: dtolnay, cjlongoria Differential Revision: D78950613 fbshipit-source-id: 3b6f8d92a53f3c734729f1c5a2ab9051c730d62c
Reviewed By: christophpurrer Differential Revision: D78949440 fbshipit-source-id: 5c5015f602b9fe591aa68f179163bd37dfb0dcff
Reviewed By: SamChou19815 Differential Revision: D78941100 fbshipit-source-id: 66d462670471212d23e8682bd5bf1ebd79ef4582
Reviewed By: pieterv Differential Revision: D79092377 fbshipit-source-id: 5dbc0de493265d8729476b366b90291f56888ad6
Reviewed By: dtolnay Differential Revision: D78929676 fbshipit-source-id: 659d1d312b5f4cb4ff7c0b888cee9c645bbbc6d4
Summary: Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action Pull Request resolved: facebook#5042 Reviewed By: captbaritone Differential Revision: D79222970 Pulled By: lynnshaoyu fbshipit-source-id: 4529e6718a7287e0ca81790a63cc7d9ab3bfb1f8
Reviewed By: evanyeung Differential Revision: D79317297 fbshipit-source-id: a320ca4e45ebce11f37a1d342f03f31fad3c6683
Reviewed By: charmainekoh-meta Differential Revision: D79399402 fbshipit-source-id: b94cd8f7d01d8f355969a970e72509538c0ea184
Reviewed By: GijsWeterings Differential Revision: D79400163 fbshipit-source-id: b0c4f10b18b99550bdf95be620187f011b62f2f7
Summary: Do not rely solely on the example. The documentation should explicitly state that the config argument must be memorized. Pull Request resolved: facebook#5033 Reviewed By: evanyeung Differential Revision: D79457303 Pulled By: captbaritone fbshipit-source-id: 790530e4f09b10a30052f78547e7a233eb4d06e7
Reviewed By: SamChou19815 Differential Revision: D79463433 fbshipit-source-id: c6f24199c7899dd618e807b2cd65b0b3673c92ce
…#5047) Summary: Fixes facebook#5045. In facebook@b208fed we upgraded schemars which changed how the json schema for the compiler config is represented. It looks like the previous representation used enums of a single string literal to represent string literals. The new version uses the [const keyword](https://json-schema.org/understanding-json-schema/reference/const) for string literals. ## Before <img width="800" height="354" alt="Screenshot 2025-08-01 at 9 39 51 AM" src="https://github.com/user-attachments/assets/66c6ca23-7707-47cf-ad4f-f4bb554b8bec" /> ## After <img width="789" height="351" alt="Screenshot 2025-08-01 at 9 39 35 AM" src="https://github.com/user-attachments/assets/36ff9995-09bf-42e9-8cdd-30c5c3633172" /> Related: facebook#5036 Pull Request resolved: facebook#5047 Reviewed By: evanyeung Differential Revision: D79452138 Pulled By: captbaritone fbshipit-source-id: 817ab1f27c5a6c415b9bac1f561291318f069409
Summary: Relay throws an error when execution and consumption occur in the same thread without a serialization boundary (no JSON.parse()). This occurs because popular execution library have prototype less object (to allow keys like constructor etc.). Relay should not assume payload has any method available. graphql-js: https://github.com/graphql/graphql-js/blob/16.x.x/src/execution/execute.ts#L298 supermassive: https://github.com/microsoft/graphitation/blob/main/packages/supermassive/src/executeWithoutSchema.ts#L201 Pull Request resolved: facebook#5043 Reviewed By: evanyeung Differential Revision: D79271386 Pulled By: captbaritone fbshipit-source-id: f68c8f789e959350afeaf01ab794053c6cba20f7
Reviewed By: pieterv Differential Revision: D79481936 fbshipit-source-id: 4decd5c92722f935a6a03b6d2205bc31b864fb5d
Summary: Minor update. Reviewed By: dtolnay Differential Revision: D79505889 fbshipit-source-id: 63561e5fb083d969e29f4296cbd343932910f92d
Reviewed By: marcoww6 Differential Revision: D79524515 fbshipit-source-id: 18b96538a62c7ae5912b1e89d2b50c1420c7eaf5
Reviewed By: marcoww6 Differential Revision: D79652708 fbshipit-source-id: 8027082b0566cca5700d40860272b7683082b275
Reviewed By: marcoww6 Differential Revision: D79672241 fbshipit-source-id: 32693b71d913c46cc62c975a9c48879c222c2abe
Summary: X-link: meta-pytorch/monarch#766 Update clap (4.5.41 -> 4.5.42) /clap_complete (4.5.50 -> 4.5.55) Reviewed By: cjlongoria, jsgf Differential Revision: D79668462 fbshipit-source-id: 3ac0d5b90bf20733812cf3bb9e5f7b269f53d71b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 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.
No description provided.