Skip to content

feat!: upgrade to @gql.tada/internal@2 - #434

Draft
JoviDeCroock wants to merge 1 commit into
mainfrom
chore/gql-tada-internal-2
Draft

JoviDeCroock wants to merge 1 commit into
mainfrom
chore/gql-tada-internal-2

Conversation

@JoviDeCroock

Copy link
Copy Markdown
Member

Upgrades to @gql.tada/internal@2 for 0no-co/gql.tada#595.

In that release, outputIntrospectionFile writes input objects' inputFields keyed by field name instead of as a tuple. GraphQLSP only calls the generator, so there are no code changes here, but the output files it writes now require gql.tada@2. That makes this a major release: gql.tada@1 projects should stay on GraphQLSP 1.x.

  • @gql.tada/internal: ^1.2.1 → ^2.0.0
  • gql.tada in example-tada and the e2e fixtures: ^1.11.0 → ^2.0.0

The lockfile isn't updated yet, because neither 2.0 version is published, so CI's frozen install will fail until then. Release order: @gql.tada/internal@2 → this PR → gql.tada@2, which should then depend on this GraphQLSP major.

Output files use the gql.tada@2 schema format, in which input objects'
inputFields are keyed by field name.
@changeset-bot

changeset-bot Bot commented Sep 26, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 87a7401

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@0no-co/graphqlsp Major

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

This branch has not been deployed

No deployments
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.

1 participant