chore: version packages

[gh-workflow-token-generator]

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 main, this PR will be updated.

Releases

@team-plain/graphql@3.0.0

Major Changes

• 17852be: The bundled documents no longer select deprecated fields on value-object types, so three fields are gone from the generated result types. No method is removed, but this is breaking in both directions and you should read the table before upgrading.

  field	TypeScript	JavaScript	replacement
  ThreadDiscussionToolCallEntryPayload.isSuccess	TS2339 at build	undefined	status: PENDING, SUCCESS or ERROR
  ThreadsDisplayOptions.hasLinearIssues	TS2339 at build	undefined	hasIssueTrackerIssues
  ThreadsDisplayOptions.hasJiraIssues	TS2339 at build	undefined	hasIssueTrackerIssues

  The compile error is the good outcome. It names the field and finds every call site for you. Plain JavaScript gets no such warning and simply reads undefined, which is why this ships as a major: on a caret range ^2.0.0 would have resolved this automatically, and a build would have broken without anyone choosing to upgrade.

  isSuccess is the one most likely to be read. Do not translate it as status === 'SUCCESS' and stop there: the old boolean read false for a call that was still running as well as one that failed, so any code treating false as failure was already mislabelling pending calls. Read status and handle PENDING as its own case.

  The generator already skipped deprecated fields everywhere else; the value-object expansion was the one path that did not, which is why these three survived. Deprecated operations are untouched, so every method the SDK exposes today still exists.

@team-plain/ui-components@11.0.0

Patch Changes

• Updated dependencies [17852be]
  • @team-plain/graphql@3.0.0

---

Note

Medium Risk
The release itself is low risk, but publishing graphql 3.0.0 will break TypeScript builds and silently return undefined in JS for consumers still reading the removed fields.

Overview
This is an automated Changesets release PR: it bumps versions, folds the consumed changeset into changelogs, and removes .changeset/sdk-300-drop-deprecated-value-object-fields.md. No SDK implementation changes appear in this diff.

@team-plain/graphql goes to 3.0.0 (major) for commit 17852be: bundled GraphQL documents stop selecting deprecated fields on value-object types, so three properties disappear from generated result types—ThreadDiscussionToolCallEntryPayload.isSuccess, ThreadsDisplayOptions.hasLinearIssues, and ThreadsDisplayOptions.hasJiraIssues. SDK methods are unchanged; consumers should use status (including PENDING) instead of isSuccess, and hasIssueTrackerIssues instead of the Linear/Jira-specific flags.

@team-plain/ui-components goes to 11.0.0 with a patch-level dependency bump to @team-plain/graphql@3.0.0 (major version alignment for the monorepo release).

^{Reviewed by Cursor Bugbot for commit ea68cc2. Bugbot is set up for automated code reviews on this repo. Configure here.}