Skip to content

Upcoming Release Changes #10222

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

Merged
merged 1 commit into from
Jan 28, 2025
Merged

Upcoming Release Changes #10222

merged 1 commit into from
Jan 28, 2025

Conversation

theguild-bot
Copy link
Collaborator

@theguild-bot theguild-bot commented Dec 23, 2024

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/[email protected]

Minor Changes

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

  • #10230 60dd72f Thanks @eddeee888! - Fix generateInternalResolversIfNeeded.__resolveReference making the resolver required

    __resolveReference's default behaviour when not declared is to pass the ref to subsequent resolvers i.e. becoming the parent. So, it means we don't have to make this resolver required.

    This patch makes __resolveReference optional when generateInternalResolversIfNeeded.__resolveReference is set to true.

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

  • #10230 60dd72f Thanks @eddeee888! - Fix generateInternalResolversIfNeeded.__resolveReference making the resolver required

    __resolveReference's default behaviour when not declared is to pass the ref to subsequent resolvers i.e. becoming the parent. So, it means we don't have to make this resolver required.

    This patch makes __resolveReference optional when generateInternalResolversIfNeeded.__resolveReference is set to true.

  • Updated dependencies [60dd72f]:

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

@graphql-codegen/[email protected]

Patch Changes

Copy link
Contributor

github-actions bot commented Dec 23, 2024

🚀 Snapshot Release (rc)

The latest changes of this PR are available as rc on npm (based on the declared changesets):

Package Version Info
@graphql-codegen/cli 5.0.4-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/visitor-plugin-common 5.6.1-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-document-nodes 4.0.13-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/gql-tag-operations 4.0.13-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-operations 4.4.1-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-resolvers 4.4.2-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/typed-document-node 5.0.13-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript 4.1.3-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/client-preset 4.6.0-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎
@graphql-codegen/graphql-modules-preset 4.0.13-rc-20250128104122-219140f9b5bdf410963b27f59e14bac52fc213e7 npm ↗︎ unpkg ↗︎

Copy link
Contributor

github-actions bot commented Dec 23, 2024

💻 Website Preview

The latest changes are available as preview in: https://976afd90.graphql-code-generator.pages.dev

@ThePlenkov
Copy link

Hi! Do you already know when next release is planned? I came here from #10155 which is exactly what I miss now. Thanks!

@theguild-bot theguild-bot force-pushed the changeset-release/master branch 11 times, most recently from 3581818 to efd34b1 Compare January 21, 2025 14:32
@theguild-bot theguild-bot force-pushed the changeset-release/master branch 4 times, most recently from abd6578 to 8556acd Compare January 27, 2025 07:19
@theguild-bot theguild-bot force-pushed the changeset-release/master branch from 8556acd to 219140f Compare January 28, 2025 10:39
@eddeee888 eddeee888 merged commit 8192a88 into master Jan 28, 2025
21 checks passed
@eddeee888 eddeee888 deleted the changeset-release/master branch January 28, 2025 11:54
@eddeee888
Copy link
Collaborator

This is now released here @ThePlenkov 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants