[JimmyPettersson85]

🎫 Ticket: https://linear.app/stream/issue/FEEDS-2164/scheduled-posts-publish-activities-at-a-future-time-api-first

📑 Docs: https://github.com/GetStream/getstream.io/pull/878

💡 Overview

Regenerates the feeds client from the GetStream/chat branch feature/feeds-2164-scheduled-posts (chat PR: https://github.com/GetStream/chat/pull/19854), which adds scheduled activities: posts published at a future time.

• New methods on the client: scheduleActivity, queryScheduledActivities, getScheduledActivity, updateScheduledActivity, deleteScheduledActivity, publishScheduledActivityNow. A client-side caller sees and manages only its own scheduled activities.
• New models for those requests and responses, plus the five feeds.scheduled_activity.* WebSocket events (created, updated, deleted, published, failed) with their decoders and event mapping.

All changes are additive.

📝 Implementation notes

• Only that branch's spec changes are included: the diff is between the client generated from the branch's merge-base with chat master and the client generated from the branch itself. Two fields reuse types (RestrictReplies, ActivityVisibility) that chat master has named but this client hasn't released yet, so they are inlined as the same string unions the released ActivityRequest uses.
• Feed's exhaustive eventHandlers map gets the five new event types as Feed.noop. They are scoped to the author, not to a feed, and the published post itself arrives as feeds.activity.added, so feed state needs nothing from them.
• Checks: tsc -p tsconfig.lib.json and yarn build pass, and the unit tests (excluding __integration-tests__, which need a backend) pass, 504 of 504.
• The chat QA tests use this branch through the same-branch-name swap. Release this before the chat PR merges, then bump @stream-io/feeds-client in chat's tests/qa/package.json. The server-side counterpart is feat: add scheduled activities (FEEDS-2164) stream-node#385.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}