chore: regenerate graphql schema and client - #40
Merged
Conversation
Update GraphQL schema from the API and regenerate documents and SDK. Co-authored-by: Cursor <cursoragent@cursor.com>
presmihaylov
approved these changes
Jul 14, 2026
mattvagni
enabled auto-merge (squash)
July 14, 2026 22:21
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
@team-plain/graphqlpackage viapnpm --filter @team-plain/graphql codegen, which downloaded the latest schema from Plain's API and regenerated_generated_documents.graphql,_generated_documents.ts, and_generated_sdk.ts.minorbump for@team-plain/graphql) matching the convention used for prior schema regenerations.Test plan
pnpm --filter @team-plain/graphql exec tsc --noEmitpassespnpm checkreports no errors (pre-existing warnings only)majorbump instead ofminorMade with Cursor