Upcoming Release Changes #10322
Merged
Upcoming Release Changes #10322
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
github-actions
bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
84c765d to
f83b571
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
f83b571 to
6c70bb9
Compare
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 master, this PR will be updated.
Releases
@graphql-codegen/visitor-plugin-common@5.8.0
Minor Changes
f6909d1Thanks @eddeee888! - Implement semanticNonNull custom directive@graphql-codegen/typescript-operations@4.6.0
Minor Changes
f3cf4dfThanks @eddeee888! - Add support fornullability.errorHandlingClient. This allows clients to get stronger types with semantic nullability-enabled schemas.Patch Changes
f6909d1]:@graphql-codegen/typescript-resolvers@4.5.0
Minor Changes
f6909d1Thanks @eddeee888! - Implement semanticNonNull custom directivePatch Changes
f6909d1]:@graphql-codegen/client-preset@4.8.0
Minor Changes
f3cf4dfThanks @eddeee888! - Add support fornullability.errorHandlingClient. This allows clients to get stronger types with semantic nullability-enabled schemas.Patch Changes
f6909d1,f3cf4df]:@graphql-codegen/typescript-document-nodes@4.0.16
Patch Changes
f6909d1]:@graphql-codegen/gql-tag-operations@4.0.17
Patch Changes
f6909d1]:@graphql-codegen/typed-document-node@5.1.1
Patch Changes
f6909d1]:@graphql-codegen/typescript@4.1.6
Patch Changes
f6909d1]:@graphql-codegen/graphql-modules-preset@4.0.16
Patch Changes
f6909d1]: