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
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.
What changed
This branch pulls in the Renovate updates from #1424 and #1426:
graphqlto16.13.2vitestto4.1.5It also includes the review cleanup from #1427 follow-up work:
src/zod_shared.ts, since both zod and zodv4 use themsrc/lazy.tsVitest 4 exposed a GraphQL module identity problem. The tests were building schemas through one
graphqlentry and@graphql-tools/*was checking them through another, which trips GraphQL-JS' realm check. The config now aliasesgraphqlto the CJS entry and externalizes it for Vitest, so the test runner uses one GraphQL instance.Checks
pnpm install --frozen-lockfilepnpm type-checkpnpm testpnpm lint