As part of our ongoing transition to the Project / Model / Version data model, several legacy GraphQL fields from the old API surface are now formally scheduled for removal on January 1st, 2026.
@insiders and developers, this post serves as both notice of these upcoming removals and clarification on where API deprecations will be tracked in the future. From now on, all GraphQL-level deprecations and removals will be listed and maintained in the public API changelog. Please refer to that page for the most up-to-date details.
Deprecations scheduled for removal on January 1st, 2026
| Field | Replacement |
|---|---|
| Activity | |
Stream.activity |
— |
| Comments | |
Query.comment |
Project.comment |
Query.comments |
Project/Version/Model.commentThreads |
Project.commentActivity |
projectCommentsUpdated |
| Streams, Branches and Commits | |
User.commits |
User.versions |
User.streams |
User.projects |
User.favoriteStreams |
— |
streamDelete |
ProjectMutations.delete |
streamsDelete |
ProjectMutations.batchDelete |
streamUpdatePermission |
ProjectMutations.updateRole |
streamRevokePermission |
ProjectMutations.updateRole |
| Server Invites | |
streamInviteCreate |
ProjectInviteMutations.create |
streamInviteBatchCreate |
ProjectInviteMutations.batchCreate |
streamInviteCancel |
ProjectInviteMutations.cancel |
streamInvites |
User.projectInvites |
Why these changes are happening
These fields belong to the deprecated Stream-based API surface. The replacements align all queries and mutations under the newer Project / Model / Version structure that defines Speckle v3.
Going forward
Future API deprecations and removals will no longer be announced individually in the forum.
They will instead be tracked exclusively in the: