docs: complete v2.0 migration guide and add announcement blog post#1808
Open
jziggas wants to merge 4 commits intoMichalLytek:masterfrom
Open
docs: complete v2.0 migration guide and add announcement blog post#1808jziggas wants to merge 4 commits intoMichalLytek:masterfrom
jziggas wants to merge 4 commits intoMichalLytek:masterfrom
Conversation
Expand migration guide to cover all breaking changes from v1.x to v2.0 (resolver loading, auth, validation, errors, scalars, custom decorators, deprecated options, nullability, build target, ESM, peer deps). Add announcement blog post for the v2.0 stable release. Closes MichalLytek#1418 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…migration guide Add "Other improvements" section to blog post covering non-breaking features: directives on interfaces/args, deprecating input fields, buildTypeDefsAndResolversSync, readonly auth roles, default value inference opt-out, implements chain relaxation, Reflect polyfill support. Add note about graphql-js v15 to v16 upgrade in migration guide peer dependencies section. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
MichalLytek
reviewed
Mar 27, 2026
Owner
|
Love it! ❤️ Thank you very much for your contribution 🙌 |
Replace the brief bullet list with a proper performance chapter covering: - HashMap-based metadata caching (O(n) to O(1) for 11 metadata categories) - Validation becoming opt-in (skipping entire middleware layer) - Glob path removal (no more dynamic require at build time) - Safe multi-schema builds (cloned metadata storage per build) - ES2021 target and graphql-js v16 improvements Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
@MichalLytek How is this? |
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
2 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.
Summary
docs/migration-guide.md) to cover all breaking changes from v1.x to v2.0 — resolver loading, auth system, validation, error classes, scalars, custom decorators, deprecated options, nullability, build target, ESM, and peer dependencies. Each section includes before/after code examples.website/blog/2026-03-26-typegraphql-2.md) for the v2.0 stable release, covering the major features and linking to the migration guide.Closes #1418
Test plan
npm run buildinwebsite/to confirm Docusaurus builds cleanly