-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: graphql 15 fixes, feature flags, tests #2091
Conversation
🦋 Changeset detectedLatest commit: 3b6a150 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as canary in npm (based on the declared |
2051769
to
ba12e41
Compare
Codecov Report
@@ Coverage Diff @@
## main #2091 +/- ##
==========================================
- Coverage 65.70% 63.32% -2.39%
==========================================
Files 85 79 -6
Lines 5106 5279 +173
Branches 1631 1665 +34
==========================================
- Hits 3355 3343 -12
- Misses 1747 1932 +185
Partials 4 4
Continue to review full report at Codecov.
|
6b536c2
to
e5a0de3
Compare
- fix graphql 15 related issues in several packages - introduce build & tests against graphql@15 - use version driven logic to make tests pass
I think this will fix a longstanding issue, especially glaring with the graphql@16 upgrade, is ensuring legacy support, and even setting the path for an eventual test matrix of
graphql
versions if we wantwithout deploy previews it doesn't feel exhaustive, but this is a good first step