Repository navigation
Version Packages - #102
Merged
Merged
Version Packages#102
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 12, 2026 20:20
36582ae to
4b314ec
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@khanacademy/graphql-flow@5.0.0
Major Changes
61123d4: Merge sub-selections when the same response name is selected through multiple branches (base level + inline fragment, two fragment spreads, etc.) so the generated TypeScript matches what the server actually returns.
Bug fix. Previously, a query like
generated a
Human.friendstype containing onlyname— theidselection from the base level was silently dropped. graphql-flow now mirrors the GraphQL spec's CollectFields behavior and merges the twofriendsselections, producing{ id; name }.Behavior change (why this is a major bump): For queries that mix inline fragments with base-level field selections on an interface, the field-lookup base is now the concrete impl rather than the interface itself. In practice this means:
Human.name's description shows up where previously only the bare interface field appeared).If you depend on the exact previous output (e.g. snapshot tests of generated
.tsfiles), expect diffs in interface-with-fragment queries. Regenerate types and review.Patch Changes
.vscodefolder, which the macOS sandbox that coding agents run in can't write intonode_modules