All releases
Fix

Social API — deprecated aliases removed (action needed if you still use them)

The one-version deprecation windows from the June consistency pass and the conversation-route consolidation are closed: the old actor parameter names, DELETE request bodies, POST /posts/views, the conversation rename route, and the conversation-level mute/pin fields are gone. Requests using them now fail with a clear 400 or 404 instead of being accepted.

If you migrated when these were deprecated, nothing changes. If not, requests now fail loudly rather than silently falling back — each error names the removed field and its replacement.

  • Actor parameter. The legacy names (requester_id, viewer_actor_id, src_actor_id, sender_id, and the deprecated caller_actor_id/actor_id body forms on DELETEs) return 400. Use actor_id — a query parameter on reads and DELETEs, a top-level field on writes.
  • Removed routes. POST /posts/views (use /posts/impressions) and PATCH /conversations/:id/name (pass name on PATCH /conversations/:id) now return 404.
  • Conversation participant state. muted / muted_until / pinned on the conversation-level PATCH return 400 — set them on PATCH /conversations/:id/members/:actorId.

@productcraft/social 0.7.0 reflects the slimmer surface, and every docs snippet now shows only the canonical shapes. This closes the second and final planned breaking window of the Social API consistency program.